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.
I was using a custom layout for my keyboard as I've a UK laptop but still use french accents sometimes. After the update from Wheezy to Jessie my configs disappeared so I have put them back:
- Defining my layout here: /usr/share/X11/xkb/symbols/gb - Adding here: /usr/share/X11/xkb/rules/base.xml and here /usr/share/X11/xkb/rules/evdev.xml in the gb configItem
Code: Select all <variant> <configItem> <name>accentsFR</name> <description>English (UK with french accents)</description> </configItem> </variant>
- Adding the declaration of the layout here /usr/share/X11/xkb/rules/base.lst and here /usr/share/X11/xkb/rules/evdev.lst
Code: Select all accentsFR gb: English (UK with french accents)
So everything looks alright, if I go to System Tools -> Preferences -> Settings -> Keyboard -> Input Source my layout is well selected and I can even see the correct layout by clicking on the keyboard icon (cf my snapshot)
Here is the snapshot of the keyboard input source settings: [URL]....
I am installing Jessie to a dual-boot Dell Inspiron 1150 laptop currently booting Windows XP + Ubuntu 9.04. I downloaded the small installation image:
Code: Select all//cdimage.debian.org/debian-cd/8.1.0/i386/iso-cd/debian-8.1.0-i386-netinst.iso and created a live dvd using growisofs.
The Jessie install documentation says: "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the MD5SUMS file that should be present in the same location as where you downloaded the image from." For the downloaded image this produced the result
There is no MD5SUMS file in the download directory. There is an md5sum.txt file included in the iso image: this lists the md5sum of every file in the image, but not that of the image itself. The check for the burned dvd was successful :
Code: Select all~$ dd if=/dev/cdrom | head -c `stat --format=%s debian-8.1.0-i386-netinst.iso` | md5sum 645120+0 records in 645120+0 records out 330301440 bytes (330 MB) copied, 1.28047 s, 258 MB/s 095a83b715e1b74b6d30b2259275f4af -
Is this a documentation error ? I next booted the laptop from the live installer dvd. After generating a number of messages, it stopped displaying a message along the lines of: "Invalid video mode - press Enter to select a mode".
I assumed it would wait for me but it soon rushed on, producing screeds of segmentation fault error messages, eventually slowing down to a rythmic display of:
Code: Select all*** Error in Xorg:free() invalid pointer: 0xb7101ce3
***Surely it should have waited for me to press Enter?
I 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.
I'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?
I'd like to create my own custom Debian live CD — the idea being to have my own rescue CD with my favorite Debian tools installed. I read about bootcd and was going to give that a try, after creating the ideal system in a qemu virtual machine.
How much exactly can you install on a system so that bootcd can still fit it on a CD? I'm presuming there is some kind of compression involved. When I tried to create my VM, I coudln't get Jessie + LXDE to install onto a 2GB virtual drive (net install) so naturally I'm wondering what I'm going to be able to put on a 700MB CD.
I 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:
Some 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 ...
I want to create a LiveDVD with lots of packages that do not exist in repos. Stuff that I built from source...
OpenFOAM with my own customized solvers and utilities, Tetgen, Netgen ,GMSH with OpenCascade support, BRL-CAD, Code-Aster, Salome Platform, Code Saturne, FreeMat, K3d...
Some of these apps have been compiled with Intel development toolbox, icc/ifort/mkl. Mainly scientific/Engineering stuff. How do I include all these packages in a custom Live Build...?
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 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.
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~ # 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-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?
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 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.
Having spent weeks perfecting my Ubuntu the way I like it, I was wondering if there is a way of preserving it as a either a liveCD or USB flash drive, with a view of using it on other PC's activated upon start up?
Possibly (under the USB option) with the option of launching from the flash drive itself, or installing onto a PC's hard drive.So, in essence, it would be a liveCD but custom made to reflect the way my Ubuntu looks and feels now? Is there any easy-to-use software available to perform such a task?
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've created a USB startup disk under Ubuntu 10.04 lucid (Live CD), Ive selected the option to save system settings to the flashdrive with about 200MB usage, now that ive configured and customized the opperating system (on the flashdrive) I want to create a ISO from that flashdrive installation.
Once the ISO is created, I want to burn it, boot off the CD then create another startup disk but this time setting "Discard on shutdown" so no settings or files can be saved to the flashdrive, but my custom setup remains. "its for an internet cafe setup".
How do i recreate an ISO from the USB startup disk?
One of my disks in my computer crashed, it was the one containing /boot and some data partitions. The other system and /home partitions were on a second disk, which is ok.
I was wondering, can I create a new /boot partition, and keep on using the rest of the system? Can I somehow do it with a chroot from a live/installer disk, run grub, and use my system again? I have another disk which I can put in the system, but there is even an unused partition on the disk which is ok (but it is rather big for /boot).
How 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.
The 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 :
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 ?
After 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.
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
When 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.
I 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?
I'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?
