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
ADVERTISEMENT
Sep 26, 2014
I have Acer Aspire S7-392. It has two 128GB SSD drives. They are using RAID 0. Currently there is Windows 8.1 installed on the RAID 0 drive.I am trying to install Debian 7.6 (wheezy) alongside Win 8.1 (dual boot). Actually I have already created linux partitions and installed mentioned Debian on my computer. I had to skip grub installation due to fatal error that had occurred. (Everything on existing RAID 0 volume).Now I am looking the way to install grub and boot Debian. I have disabled UEFI Secure Boot. It didn't work.
My question is:
1. Is it possible to have Win 8.1 and Debian dual-bootable on the same RAID 0 volume? How to install grub and boot debian?
2. If not, what am I supposed to do to achieve what I want (these two systems on one computer)? Delete old one RAID 0 and create two new: one for windows and one for linux partitions?
View 0 Replies
View Related
May 27, 2015
I have Debian installed but I need to dual boot with distribution based on Ubuntu 14.04. This is my first UEFI dual boot install attempt. And I must do it right. I must not lose my Debian !
Code: Select allDisk /dev/sdb: 232,9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
[Code] ....
Ubuntu will go to /dev/sdb5 but I don`t no for sure what to do when installing Ubuntu. How to select during install existing UEFI partition(/dev/sdb1) so Debian and Ubuntu can use it. Can I select existing UEFI partition like I would do for /home or /swap ? Will this work ?
And what will happen with Grub if I select install grub ? I want to manage grub from Debian, it is my main OS. Can I skip Grub install and just update grub on my debian after ubuntu install ? Or I just install grub, then after completed Ubuntu install I install it again from Debian. Will this work ?
Is procedure of installing dual boot trivial like before or UEFI hide`s some unpleasant surprise.
View 8 Replies
View Related
Dec 15, 2015
I'll start off with stating my problem and summarize how I got to it.
I installed Windows 10 on an SSD. I installed Debian 8.2 after it. The SSD was/is a GPT disk. I installed both installations from a UEFI booted device (DVD for Windows, and USB drive with Live CD for Debian).
I tested it after each installation making sure I could boot via UEFI into Windows, then Debian, then Windows, to make sure nothing broke.
I rebooted the machine. Suddenly, no more UEFI. Nothing. I didn't change any BIOS/UEFI setup menu settings. Not even my USB drive with Live CD will boot through UEFI anymore. Even when nothing else is plugged into the system.
My situation is actually a bit more complicated than that, but I think that will suffice for now. I can still boot into the Live CD on the USB drive, just in Legacy mode only. I mounted the EFI partition on /mnt/boot after I mounted the file system for Debian on /mnt. It is identical, as far as I can tell, to as it was before when it was working.
My motherboard has CSM and Secure Boot, both have been set up how they need to be to boot UEFI into Debian. Tinkering with them further after things broke did not fix it. I tried all variations of options/settings.
The GRUB Reinstall guide says to be in EFI mode before starting it, so I can't do that.
My motherboard is an ASUS X99 Deluxe, and I've heard ASUS has special "features" (read: bugs) that come with their boards. Searching hasn't brought up any other people with this issue. I believe the firmware is updated to it's most current one.
I've tried dd-ing my backup of my old system, from before trying to migrate to a Dual Boot system, to the SSD (after backing up the dual boot setup with dd -> <name>.img via the Live CD USB). However, that won't boot either as it is a UEFI install as well.
The layout of my EFI partition is as such:
/boot/EFI/Boot/bootx64.efi
/boot/EFI/Microsoft/<Microsoft-naming>.efi
/boot/EFI/debian/grubx64.efi
I've heard that the standards on how that's supposed to be set up isn't a standard. However, since it worked booting into the OS' the first time, I don't see how that could be the issue (a bad hierarchy layout leading to the UEFI not being able to see the OS installs).
I've seen that I can boot to an EFI shell (called Shell.efi, apparently) via an option in my UEFI BIOS setup menu on my motherboard. Is that an option here to somehow bypass this strange issue?
All I can think to try is burn it all and start over. But not knowing what caused it means I could just make it happen again. Plus, I can't boot into UEFI install media, so I can't install UEFI boot OS'. :/
View 5 Replies
View Related
Feb 15, 2016
As you probably know Debian LIVE ISOs is not (U)EFI bootable since there is no EFI bootloader on them. I need to boot usb for uefi mode...
View 3 Replies
View Related
Dec 23, 2014
My Toshiba Satellite C870-198 has Debian 7.7 installed in UEFI mode alongside Windows 8.1. The GRUB menu no longer displays, but the machine boots straight into Windows.
I can boot into Debian or Windows from rEFInd installed on a USB stick. The rEFInd menu has the following entries:
The Debian entry actually launches the GRUB menu which was installed with Debian.
Code: Select allBoot Microsoft EFI boot (Boot Repair backup) from Basic data partition.
Boot supposed Microsoft EFI boot (probably GRUB) from Basic data partition.
Boot EFIubuntugrubx64.efi from Basic data partition.
Boot EFIdebiangrubx64.efi from Basic data partition.
Boot bootootx64.efi from Basic data partition.
Boot vmlinuz-3.2.0-4-amd64 from boot.
In an attempt to fix GRUB I executed the commands in the 'Reinstalling grub-efi on your hard drive' section of: [URL] ....
Code: Select allmount /dev/sda1 /boot/efi
... surprisingly returned:
Code: Select all$LogFile version 2.0 is not supported. (This driver supports version 1.1 only.)
$LogFile version 2.0 is not supported. (This driver supports version 1.1 only.)
Did not find any restart pages in $LogFile and it was not empty.
The file system wasn't safely closed on Windows. Fixing.
Code: Select all[ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
... returned "EFI boot on HDD".
[Code] ....
... Where is Debian?
FULL HISTORY ....
=============================
The laptop came with Windows 8 preinstalled. I switched off Secure Boot and installed Ubuntu for UEFI dual boot. I recall having to use Boot Repair to get the GRUB boot manager working properly for both systems.
Recently I decided to replace Ubuntu with Debian 7.7 and first cloned the entire hard drive to a USB drive (The Clone Drive). This drive successfully boots into Ubuntu in UEFI mode.
Following this I took the opportunity to update Windows to 8.1, which broke GRUB as expected, so that the machine would only boot straight into Windows.
I installed Debian from a live USB stick in the mistaken belief that it would be bootable in UEFI mode. It did boot OK in legacy mode.
I then burned the full Debian 'DVD' image to a USB stick, booted it in UEFI mode and reinstalled Debian. In UEFI mode GRUB allowed me to boot into both Debian and Windows.
At this point I tested The Clone Drive. It was still able to boot into Ubuntu as previously, but after powering down, unplugging The Clone Drive and rebooting, the GRUB menu failed to appear and the machine booted straight into Windows. This is its current state.
View 13 Replies
View Related
Sep 18, 2015
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?
View 1 Replies
View Related
Sep 12, 2014
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 Related
Mar 24, 2015
I've set up a dual boot system with Debian and Windows 8, both installed on their own drive, with their own boot partition. I installed eveything in UEFI-Mode with fast- and secure boot turned off. Both installations are working, as I can access them by changing the boot priority in the Bios. What I cannot achieve is to let grub boot my windows installation.
This is the output of parted -l:
Code: Select allModel: ATA Samsung SSD 840 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 512MB 511MB fat32 boot
2 512MB 111GB 111GB ext4
3 111GB 128GB 17,0GB linux-swap(v1)
[Code] ....
As you can see, my linux install is on sda, my windows install on sdc (sdb beeing a data disk). This is the entry I made in the 40_custom file in etc/grub.d:
Code: Select allmenuentry "Windows 8.1" {
insmod part_gpt
insmod chain
set root='(hd2,gpt2)'
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
boot
}
I think this should be fine, but if I choose the windows entry wehen grub is booting, it says: error: no such partition. It's my first debian installation, and I am stuck here. Not too much of Linux experience in general.
View 12 Replies
View Related
Nov 20, 2015
I just installed Debian jessie on my Dell Latitude E6410 using the UEFI install. No everything went well during the install, but after the install the first boot i ran into an issue that the laptop will not boot.
When I go in to the boot menu of the Dell Latitude E6410, I see that debian has created a uefi name (Debian)
When I select this, it boots without any issues. After again a reboot again, no luck still a black screen during the boot.
Seems that the only option to get my laptop booting is by pressing F12 and select Debian in the UEFI boot of the laptop.
Is there any way i can get my laptop to boot Debian directly from UEFI, without having to press F12?? (Also disabled all legacy devices to start up but no luck)...
- Debian Jessie X64 (Using 32/64 network install, via USB)
- Dell Latitude E6410 i5 (1280x800 intel graphics) latest bios A16
- SSD drive (Samsung 470 series)
- Debian is the only OS installed
View 1 Replies
View Related
Feb 17, 2016
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.
View 9 Replies
View Related
Aug 29, 2014
I appear to have the exact problem that is currently listed in the 7.6 errata about EFI boot and black screen while trying to install ("Potential issues with UEFI booting on amd64"). The problem is that their workaround is not an option for me. This is a new rig and the motherboard doesn't appear to have any kind of ability to disable secure boot. I also don't know if my problem is exactly what they're thinking when it comes to that entry.
I'm able to get to the Grub install screen where you have the option to install Debian but when I select an option (any option) the screen turns off, back on but is black. All activity in the system stops after a few seconds (3-5 seconds) and that's it, she's done. I've tried all the options to try and disable secure boot but the options listed below are as close as I can get (and apparently should be sufficient).
The CD ISO used was the 7.6 netinst CD. I've also tried the Jessie ISO (Testing) that was downloaded about 2 hours ago. Same results. Unlike the errata which says "intermittent booting problems", my issue is consistently reproduced with no other result no matter what I do.
The rig:
-Asus H97-Plus running revision 2202
-Intel i5-4570
-32GB DDR3-1600
-128GB SSD Drive
-No external video card - using on board only but have tried both VGA and HDMI ports with the same result.
BIOS settings (is it still called BIOS or is it UEFI now?)
-Fast Boot: Disabled
-Launch CSM: Enabled
-Boot Device Control: "Legacy OPROM Only" or "UEFI and Legacy OPROM" (tried both)
-Secure Boot State: Enabled (it's grayed out and I'm unable to change this)
-OS Type: Other OS (supposedly makes it so you can boot non-Windows OS)
The Debian page with the errata: [URL] ...
Look for "Potential issues with UEFI booting on amd64"
The obvious suggestions I've tried:
-tried USB boot & CD boot - same result
-tried altering the grub script to add the ACPI options - no effect
View 1 Replies
View Related
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
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
Jun 20, 2011
I've installed squeeze and wheezy on an old Toshiba Satellite 210 CS laptop with 48MB RAM and a 20GB IDE harddrive.Grub2 won't boot at all and stops with a "error: cannot allocate real mode pages". The solution to that is to use the grub-legacy package.The boot then fails with "waiting for root device" and drops to an initramfs shell.
View 5 Replies
View Related
Jun 18, 2015
On a new Lenovo Thinkpad T450s, I encounter the following issue: The USB drive containing live CD image ("burned" to the USB using mkusb tool --> which in turn uses dd) cannot be booted from the UEFI boot loader. I have to reconfigure the hardware (BIOS) setup to support both UEFI & legacy system, and with first boot priority given to legacy (BIOS-style) booting. But if I do this, I don't see the UEFI system in the /sys/firmware/uefi directory. I am using the 64-bit live CD image (debian-live-8.0.0-amd64-xfce-desktop.iso).
This is my goal: to boot the live USB from UEFI, so that I can install it in a form that is UEFI-bootable.
View 3 Replies
View Related
Mar 21, 2015
On Windows OS, I can create Debian UEFI USB boot by mount Debian ISO and directly copy content of ISO to USB FAT32. On Debian OS, When I mount the debian iso and directly copy content of iso to usb fat32, I keep getting this error: "Filesystem does not support symbolic links".I choose to skip all, the copy operation continue but USB can't boot.
Question: How to create Debian USB UEFI boot by copying content of iso file directly to fat32 usb on Debian OS?My OS: Debian Jessie RC1.The ISO file: debian-jessie-DI-rc1-amd64-DVD-1.iso URL....
View 4 Replies
View Related
Oct 5, 2010
I'm trying to test out UEFI boot and install with Fedora 13. It looks like it is not supported...at least not in the standard x86-64 DVD image. Running 'dumpet' on the .iso shows no EFI boot section (whereas, for example, RHEL6 Beta-2 x86-64 DVD .iso does show one); see output below. Will there [ever] be UEFI supported boot/install CD/DVD .isos for Fedora?
[Code]...
View 1 Replies
View Related
Aug 16, 2011
I tried to install Ubuntu 11.04 on my 3 TB hard drive but UEFI firmware can't boot that Linux partition anywhere and went Windows 7 instead. Does anyone have any solutions for UEFI booting? I think EFI filesystem is messed up or bug in installer. Earlier I was able install and boot linux partition with both linux distros (Ubuntu and Fedora) before I removed them for re-install them later and created additional NTFS partition until now.
However, I was only able boot Ubuntu 11.04 from USB stick in UEFI mode. I will continue to use live USB until all solutions are solved. UPDATE: I made a data backup on one of NTFS partitions and removed it. I tried to install Ubuntu 11.04 below 1 TB disk space but still can't boot it.
My system configuration is:
ASUS Maximus IV motherboard
Intel i7-2600K processor
8 GB memory modules
Hitachi 3 TB hard drive
MSI HD 6870 Hawk video card
View 5 Replies
View Related
Sep 30, 2014
I have this new computer (MSI Ge70 2PE Apache Pro) that came with Windows 8 and UEFI. I freed space to make a partition to install Debian testing 64bits on the same HD where Windows is. I had no problem making the partition but after that I tried making a bootable usb to install Debian using the dd command and it didn't work. So I tried with an install dvd and even when I changed the boot order in the bios it didn't work.
After reading some more I realized that there could be a problem trying to boot a normal installation dvd with UEFi so I disabled Secure Boot and then switched the boot mode on my Bios to UEFI with CSM. Again it didn't work and it booted directly into Windows. So I switched the boot mode to Legacy. This time Windows didn't boot directly but I get a "Reboot and Select proper Boot device" message on a black screen.
I now realize that I need to install a UEFI "version" of Debian along the UEFI version of Windows 8. I guess that's why it didn't work with the Legacy boot mode. URL...The installer does not provide a convenient way to install an UEFI boot loader, so you are going to install a regular BIOS boot loader at first, and switch to UEFI later.
Use the expert mode and format your hard drive with a GUID Partition Table (GPT). Create a small partition (1 MiB would be far enough), type it as a BIOS Boot Partition (this is the untitled flag above the “bootable” one in Partman), do not format it and do not mount it: this will be needed for BIOS booting. Create another small partition (same kind of size), type it as an EFI System Partition (this is the“bootable” flag), format it as FAT and mount it on /boot/efi: this will be needed for UEFI booting.
View 6 Replies
View Related
Aug 22, 2014
I tried to install the latest version of Debian from a Live USB on my new laptop (UEFI). Everything goes well during installation (EFI partition, grub-efi, etc), but after restart, my computer does not boot into HDD.
How to debug the problem or fix the boot loader. What is the problem in standard installation? and how can I fix the boot loader?
View 3 Replies
View Related
Jul 29, 2015
My computer's recent history in chronological order:
1. debian jessie is installed using netinstall iso to sda.
2. windows 8.1 is installed to sdc.
Now "lsblk" returns:
Code: Select allNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
├─sda2 8:2 0 244M 0 part /boot
└─sda3 8:3 0 111.1G 0 part
└─sda3_crypt 254:0 0 111.1G 0 crypt
[code]....
Result: My computer boots directly to Windows 8.1. If I press F7 during first seconds of boot and choose "debian" as the boot device (via blue bios screen, not grub), debian boots.
My purpose:
1. To use debian grub screen to choose between debian and Windows. (To avoid pressing F7 during boot to use debian)
2. Set debian as default OS in grub and boot to debian unless I choose otherwise in for example 10 seconds.
I guess that I should update grub to fix this but I don't want to take risk.
View 12 Replies
View Related
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.
View 4 Replies
View Related
Jan 30, 2015
I'm trying to install debian and when the installer starts it UEFI at the top, instlal completes however on reboot it says 'no operating system found' i've read it can be because of UEFI but I have tried different bios options but to no avail.
Bios options
Sata mode: AHCI/IDE (haven't tried IDE yet)
Tried various combinations of the below
CSM: enable/disable
Boot Priority: Auto/legancy first/uefi first
Quick Boot: enable/disable
Boot up Num-lock Status: on/off
View 14 Replies
View Related
Oct 2, 2014
So I managed to install Debian Jessie on a MSI G70 2PE Apache Pro that came with Windows 8.
First I partitioned some space on the laptop. Then I put on the net install cd for Debian and installed it on UEFI mode. It installed correctly.
Now I'm on Grub and when Debian tries to boot it gets stuck on "Loading initial ramdisk". The cursor under it doesn't even blink. The only way to get out of there is by Ctrl-Alt-Delete. Secure Boot is turned off. Fast boot is also off. If I try to boot on recovery mode gets stuck all the same.
The options on my grub are
Debian GNU/Linux
Advanced options for Debian GNU/Linux
Windows Boot Manager (UEFI on /dev/sda2)
System Setup.
If I choose the Windows option, Windows boots, no problem.
If I choose the edit option for the Debian entry this is what it shows
Code: Select allload_video
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
[Code] ....
What is happening and what should I try to make this work? Could it be a graphics card issue since this computer has a Nvidia Gpu?
View 1 Replies
View Related
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
May 17, 2011
I'm running Debian Wheezy x-86 32 bit Kernel 2.6.38-2-686 and I have encountered a problem I'm hoping to get some help with. All help would be greatly appreciated as researching this issue has not led to any concrete information. After a reboot or similar, the process will go through the boot sequence including giving me the option of what kernel to run either 2.6.32 or 2.6.38 and starting module's as well as performing POST and then when the logon screen should appear I'm presented with a flashing cursor. I can boot into saftey mode and the CLI, but not being very efficent with Bash and the CLI I'm not sure where to go or what to do.
View 14 Replies
View Related
Jun 21, 2015
After the latest update of Debian Wheezy, about three days ago, one of my machines won't boot anymore. The update was done by:
Code: Select all/usr/sbin/update-smart-drivedb
apt-get update
apt-get -y upgrade
apt-get -y autoremove
I get the error message: "Alert! /dev/disk/by-uuid/71c... does not exist. Dropping to a shell!"
The dir /dev/disk contains only "by-id" and "by-path".
I booted with the rescue system, dropped into a shell and recreated the ramdisk with
Code: Select alldpkg-reconfigure linux-image-3.2.0-4-amd64
dpkg-reconfigure grub-pc
But without success. On another machine the update went flawlessly.
View 7 Replies
View Related
Sep 25, 2015
I decided to update all the software on my computer. Fortunately, it upgraded kernel version 3.14 to 3.16. I was happy to learn that suspend now worked on my laptop by calling pm-suspend, but it did not worked by closing the lid. So I search and found on debian's website that installing systemd and adding some config lines in /etc/systemd/logind.conf would sove the issue. So I followed the procedure and did like instructed, to end up with a computer that boots on black screen.
The last verbrose line I see on boot up is "kvm disabled by bios" and then it shutdown down the screen. The computer works, as I can login and shutdown by doing those operation blindly.
I tried removing systemd but it still does not work. If I use the old kernel 3.14 I can boot without any problem, but if I use kernel 3.16, I boot to a black screen. I remember successfully booting in 3.16 before installing systemd.
View 4 Replies
View Related
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
