Debian :: How To Stop Raising Network During Boot (Jessie)
Jul 3, 2015I have installed debian jessie with debian first disk. During boot i see a service starts to raise network. It takes time. How can i stop it?
View 1 Replies
ADVERTISEMENT
Debian Configuration :: How To Stop Mode Switching At Boot Under Jessie
Mar 19, 2016I upgraded a wheezy box in qemu to jessie (without systemd!) and now I didn't get an output from the console to a hostterminal using curses.System and grub starts with terminal output, but after around 6 to 8 lines of output the terminal gets black. As far as I found out it seems that the init process switches to graphical output. I tried out all found kernel options from nomodeset up to nofb,Are their other options to stop switching to framebuffer and graphical mode.
View 0 Replies View RelatedDebian Multimedia :: Graphics Stop Working After Upgrade To Jessie
Oct 17, 2015I upgraded from wheezy to jessie, but now I just boot to a console. I've gone through and made sure all packages are up to their latest versions, and I've made sure gnome, xorg, and xserver-xorg are reinstalled (during the upgrade they got uninstalled..).
Here's what happens when I run startx manually:
Code: Select allcharlie@asimov:~$ startx
X.Org X Server 1.16.4
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[Code] ...
Note also that this whole time, gdm3 has been running:
Code: Select allcharlie@asimov:~$ ps ax | grep gdm3
1058 ? Sl 0:00 /usr/sbin/gdm3
3993 tty2 S+ 0:00 grep gdm3
charlie@asimov:~$ sudo service gdm3 status
[Code] .....
I'm not sure why it prints that it's starting gdm3, but it does that every time I run `sudo service gdm3 status'.
Here's a copy of my /var/log/Xorg.0.log.
Debian Configuration :: Jessie Service Script Not Calling Status And Stop Routines
Apr 1, 2016I am the author of an internet radio for the Raspberry PI originally running on Debian Wheezy. The radio (radiod) service is started and stopped using the usual service commands:
service radiod start|stop|status
Since upgrading to Debian Jessie the service status and stop routines in my radio daemon are no longer called.
For example:
# service radiod status
● radiod.service - LSB: Raspberry PI Radio Daemon
Loaded: loaded (/etc/init.d/radiod)
Active: active (running) since Thu 2016-03-31 20:17:07 CEST; 15h ago
Process: 380 ExecStart=/etc/init.d/radiod start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/radiod.service
└─603 python /usr/share/radio/ada_radio.py start
If I call my program (which runs as a daemon) I see the status message from my program
# ./radiod.py status
radiod running pid 603
I have established that service stop never calls my program routines to shutdown the radiod daemon when the system is rebooted (I see that from my log files).
The reboot hangs for about 5 minutes whilst stopping the radiod service (because stop never calls my stop routines).
Below is my radiod script, which is fairly conventional, and which has been working all the time until I ported to Debian Jessie.
/etc/init.d/radiod
#!/bin/sh
#
### BEGIN INIT INFO
# Provides: radiod
# Should-Start:
# Should-Stop:
[Code] ....
Debian Configuration :: Raising The APT Cache Limit?
Nov 4, 2010When adding repositories, I ran up past the default apt cache limit of 25165824. I found a couple of sources - one that treats apt.conf.d as an individual file, and another that treated it as a folder - which my system does.
Following those guidelines, I went into /etc/apt/apt.conf.d/debconf70 to add a line of code that sets the default to 2x and 4x that limit, and... well, apt doesn't seem to recognize the difference.
Here's the code I added at the end:
So, is there somewhere else that I need to change things? Am I completely off on this? I found a year-old thread on this error in the ubuntu forums, where a gentleman who is now a member of the staff simply suggested to the op "take out that debian repository you listed". It kinda negated the premise for me, you know? I'm kinda hoping there's more that I can do.
Debian :: Jessie 8 Update - Boot Grub Shows Now 2 Kernel Versions To Boot From
May 2, 2015After some updates Jessie 8 my boot grub shows now 2 kernel versions to boot from.
3.16.0-4-amd64
3.16-3-amd64
- How do I know which one is the newest and if happy with it, how to remove the older one?
Debian Installation :: Boot Jessie Without Legacy Boot
Nov 8, 2015I've been using linux distros on my desktop forever, and got a windows 10 laptop recently. I want to dual-boot debain (jessie), so I installed it and it worked fine. Unfortunately, I have to enable Legacy mode in BIOS to boot into my grub then linux machine. Is there a way I can have my computer boot without legacy boot?
View 2 Replies View RelatedDebian :: Disable GUI In Jessie At Boot
May 17, 2015How do you disable startx in Jessie when it boots up? In Wheezy I just had to disable the gdm3 service. I also tried a few settings in grub, but it still starts.
View 7 Replies View RelatedDebian :: How To Actually Boot With SYSV On Jessie
Jul 26, 2015The grub boot loader offers in options to boot with sysv instead of systemd. The problem is that it seems to fail and fallback to systemd. Let's have a look on my dmesg :
Code: Select allroot@PCALAIN:~# dmesg | grep sysv
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=UUID=6740d56f-604c-4920-8c64-868e23976be4 ro rootflags=subvol=__active/root init=/lib/sysvinit/init
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=UUID=6740d56f-604c-4920-8c64-868e23976be4 ro rootflags=subvol=__active/root init=/lib/sysvinit/init
[code]...
So, how to successfully boot with SYSV ? Of course, the package sysvinit is installed on my system.
First, I have done a snapshot. Nevermind, is the following safe and the correct way to go back to SYSV :
Code: Select allapt-get purge systemd sysvinit
apt-get install sysvinit systemd-shim
Is it necessary to purge and reinstall sysvinit in order to guarranty configuration updates or on the contrary, will I break my system if it has none of systemd nor sysv ?
Debian Installation :: Jessie Won't Boot
Sep 26, 2015I have two desktops running wheezy for years without problems. Recently, I reinstall jessie on one of them and won't boot anymore.The hardware is pretty normal: Asus motherboard, 12GB RAM, Nvidia video card, SSD hard drive, .After the install of jessie finishes, the very first boot failed, which means it hung up forever. The part that is annoying is that it fails at different places whenever I try.
For example, something, it fails at the following:
[ OK ] Started LSB: REP portmapper replacement
[ OK ] Reached target RPC Port Mapper
Starting LSB: NFS Support files common to client and server
Sometimes, it failed at start job is running for lsb set console font.It even failed to the console. When it goes to the console login, I can't put any user name or password. It's all frozen.The problem appears to be video card problem. But it worked fine in wheezy.
Debian Configuration :: No Network After Reboot Of Scratch Install Of Jessie
May 2, 2016I've been using various distros of Linux for over 20 years - but I'm stumped.
Was running Mint. But after taking an update a few weeks ago the network stopped working. After a lot of time and effort decided to give up on Mint and switch distros to Debian 8 Jessie.
But after changing the Network settings from default DHCP to my usual IPV4 static 10.net configuration and rebooting the network will not work.
I have several systems on a 10.100.0.0/16 LAN behind another Linux system acting as firewall/gateway.
Now, after about 7 hours of mining the Internet, I still can't get basic networking to work:
- Have tried a few combinations, with and without Network Manager and eth0 in interfaces
- /etc/network/interfaces is configured with a static IP and relevant parameters
- ifconfig shows eth0 and the correct information
- netstat -rn shows the basic default route to the gateway
- have tried with IPV6 enabled and disabled; it is not used on my LAN
The box is a desktop system, ASUS Maximum VI Formula mobo with onboard Ethernet, dual GTX 780 cards. Nothing very weird.
It all LOOKS right, but ping can't get off the box "destination unreachable", and no other system on the LAN can ping it.
I'm amazed a basic static IPV4 network setup completely breaks it. This is my main workstation - a dual-boot system where Windows runs fine - so it's not hardware.
EDIT: This has been solved. See the solution post: [URL]
Debian :: After Update Jessie Hangs During Boot
Oct 12, 2014After my most recent update, the boot sequence hangs at:"a start job is running for Create Volatile files and directories" with a timer and no limit .. I let it go for 12 minutes, but nothing.It seems as long as this sequence remains, the boot process does not finish and just hangs here.I haven't been able to find anything specific to this. I currently cannot boot into this machine, though do have access to files via dual boot.
View 8 Replies View RelatedDebian :: Wheezy To Jessie Upgrade Will Not Boot
May 28, 2015With "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?
Debian Configuration :: Fsck On Boot Jessie 8.1
Jun 25, 2015I use debian jessie 8.1 and when i boot it, pc start fsck block clean etc.. but the fsck control is activated every on boot?
View 14 Replies View RelatedDebian Configuration :: How To Get Boot Log On Jessie / Stretch
Oct 14, 2015When i'm tried google there is lots of bootlogd related document there. [URL] .... Yes there is documentation. But I'm only need "enable boot logging","reading boot log". Bootlogd not worked on jessie/stretch.
View 4 Replies View RelatedDebian Configuration :: Connect Jessie To Windows Share - Network And CIFS
Dec 4, 2015I try to connect my Debian Jessie to my Windows share
This is what I have done:
-> 1 - create an .smbcredentials file located in my /home directory (with account / password and domain)
-> 2 - implement /etc/fstab with information like that :
//192.168.x.x/Animes/media/Animes cifs uid=toto,dir_mode=0777,file_mode=0777,credentials=/home/.smbcredentials,iocharset=utf800
and when I try to go on my windows share, I have this message:
An error occurred while accessing 'Home', the system responded: mount: only root can mount //192.168.x.x/Audio-Video-01 on /media/Audio-Video-01
I think about one thing, if uid=toto is different in fstab than my current debian account session name, it is possible the problem came because of that?
(fstab, uid=toto and current session titi)
Debian Installation :: Upgraded To Jessie 8.2 Now Boot Hangs
Dec 4, 2015I had Debian 7.9 up and running like a charm until yesterday. Today I did the upgrade to 8.2, now boot hangs. I see 3 boot entries for the new kernel now -
Debian GNU/Linux, with Linux 3.16.0-4-amd64
Debian GNU/Linux, with Linux 3.16.0-4-amd64 (sysvinit)
Debian GNU/Linux, with Linux 3.16.0-4-amd64 (recovery mode)
The latter 2 entries have no problem booting up. So do the previous kernel(3.2.0.4) entries. Only the first one hangs, for which I see these 6 lines on the console:
[ 0.214704] pnp 00:04: can't evaluate _CRS: 12298
Loading, please wait...
fsck from util-linux 2.25.2
/dev/mapper/myhost-root: clean, 198627/61000000 files, 2160052/24412 blocks
[ 0.047141] kvm: disabled by bios
[ 0.000985] kvm: disabled by bios
How can I make it boot up like others?
Debian Installation :: Can't Choose Jessie In Boot Time
Feb 29, 2016Some thing quite bad happened to me , i installed debian jessie about 2 month ago. Today I wanted to try what a gnu/linux is like so I installed dragora 2.2 on one of my free partitions , (sda 1 is my debian root , sda2 is my debian home, I had sda4 which nothing was on it so i installed dragora on it. But something bad happened , during boot time you get this page which asks you what distro you want to enter in past I had just one choice and it was debian jessie, I expected after installing dragora I will see 2 distros on this page, but i get just 1 , and that's dragora ... but maybe i should mention this that when entering dragora i can access all my previous files , debian systemfile , debian home , they are still there but i can't enter debian jessie ...
View 2 Replies View RelatedDebian :: Dual Boot - Windows 7 And Jessie SSH Authentication
Jan 28, 2016I have set up authentication when I am logging from my laptop using windows 7 (putty) into Debian server (see this post [URL].....) but since my laptop is dual boot (Windows 7 and Ubuntu) how would I set up authentication when i am using Ubuntu since from Ubuntu I will be logging into Debian SSH as same user that I am when logging from windows?
View 1 Replies View RelatedDebian Configuration :: Slower Than Usual Boot In Jessie
Feb 22, 2016I've recently noted that the boot process in my Jessie installation is occasionally taking longer than usual, not dramatically as in "really hanging", but still noticeably slower, during which some messages are printed along the lines of
Code: Select alla starting job is running (2 of 5) and also after that, once lightdm (I'm using the MATE desktop) comes up the screen gets painted slower as well.
Unfortunately, once the system is up and running there's no longer trace in the logs (either traditional syslogs or journalctl) of such messages, however what comes to mind is that I've just recently enabled persistent logging in systemd: could this be the reason of such (occasional) slower boot process?
Other than that, what else could cause such behaviour? What should I eventually check to ensure things are OK?
Debian Hardware :: How To Boot Live Jessie On Aspire E15
Dec 28, 2015I'm new on this forum, but not new on linux and in general on Ubuntu and Debian and I've always programmed on these OS but I still have a long way, however, in fact I have a new Aspire E15 573G in which there is the UEFI that creates many problem on the boot of different systems but I need to change Windows 10 to Debian or to have both them because I hated Windows.
I searched in many sites to find because my debian live charged on my usb pen doesn't boot in any manner, I read that the live debian still does not start on UEFI systems but I still BELIEVE that there is a method to boot it up and I found this: [URL].....
So my request to you for now is what are the boot parameters to set to the liveboot.nsh? because that configuration doesn't solve the problem, Debian wanted ACPI disabled so I modified the .nsh but still there's the black screen.
Debian Installation :: Failed Wheezy To Jessie Upgrade (cannot Boot)
Aug 13, 2014I 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.
Debian Installation :: Boot DVD Don't Work - Jessie With Added Firmware
Jul 10, 2015I would like to upgrade from Win8.1 to Debian 8. This post might require some Wind expertise as well. I have to deal with the dreaded UEFI interface.
I got the iso with the added firmware from here: [URL] ....
The i386 download and it appears to be 334 MB. I pretty got it because I don't want to mess with the wireless controller (been there done that.)
As far as the Wind side goes I disabled secure boot. Just whenever I get to the fancy blue screen, I select boot from EFI DVD. Then it just says it can't load it and asks if I want to continue loading the OS. This might be useful I used the default Desktop Burning Gadget to burn the disk image.
Debian Installation :: Cannot Boot Into Windows XP After Dual Jessie Install
Sep 4, 2015I 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?
Debian Installation :: Live Image Jessie Do Not Boot UEFI
Sep 18, 2015Debian-live-8.2.0-amd64-xfce-desktop.iso do not boot in uefi mode. I would like to know if live image can boot uefi mode? If not how can I do later from bios to install grub efi?
View 1 Replies View RelatedDebian Configuration :: RAID1 On Jessie - Unable To Boot From Second Drive
Jul 28, 2015Recently tried to make RAID1 on MBR partitions scheme on Debian Jessie - debian-8.1.0-amd64-DVD-1. The issue - I have unable to boot from second drive after grub-install /dev/sdb by any ways. RAID1 itself for / swap and home is fully functional. Decided to try the same thing on GPT, same story. How to boot from second drive on most recent Debian Branches?
View 9 Replies View RelatedUbuntu Networking :: Stop Network Manager From Starting On Boot?
Jul 10, 2011I would like to stop network manager from starting up on boot. I have tried moving
Code:
/etc/init.d/network-manager stop
to rc.local and it did nothing but boot me into the CLI
I have also tried to put
Code:
sudo service network-manager stop and that did nothing also.
After I get network manager to stop on boot up. How do I make it so it will not auto connect to networks? My computer keeps on joining a different network on boot up. And I don't like this as some times I go to my banks website and I am on there network with out realizing it (because of the auto connect) Is there a way to stop this also?
Debian Installation :: Creating Boot Script For Custom Commands In Jessie
May 11, 2015 I didn't change anything; it just stopped working on boot. I've changed permissions according to messages from log files. No good.I now get messages saying "unable to open display ' '." If I set the display (I've done this several ways, the messages say "unable to open display ':0'."
Systemd is taking control of everything basic, with almost no documentation and no configuration tools at all: rationalization by lunatics.You can make a script to run commands on boot using systemd on Jessie by creating two files: the script, in any location a file in /etc/systemd/system that runs that script..My script is called james-boot.service, placed in my /home/james/.bin directory.
#! /bin/sh
# this is run by /etc/systemd/system/james-boot.service
# Enable with sudo systemctl enable james-boot.service
# Check with sudo systemctl status james-boot.service
# If it says the service is loaded, it's OK -- inactive only means it's done running.
[code]....
This file must have ownership root.root, with (apparently) permissions 664 (rw-rw-r--).After creating, enable with sudo systemctl enable james-boot. service.Check with sudo systemctl status james-boot.service. If it says the service is loaded, it's OK -- "inactive" only means it's done running.
Debian Installation :: New Jessie Install Black Screen On Boot (AMD Video)
May 14, 2015I 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.
Debian Installation :: Jessie UEFI System Boot Menu Missing?
Feb 17, 2016I have installed Debian Jessie 8.0.3 64-bit net install on an IBM ThinkCentre. I have earlier had a dual boot Win 8 and Ubuntu 14.04 installed on the computer. When I installed Debian Jessie, I deleted the Ubuntu partitions and created new partitions from the free space. The install went fine and the Debian EFI/UEFI version of Grub was installed, but clearly at some other place, as when I boot the system, the old Ubuntu Grub pops up and of course cannot find the necessary files that it is looking for.
View 9 Replies View Related