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?
View 1 RepliesI 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?
How to configure Web authentication against RADIUS server on Debian Jessie, because the package libapache2-mod-auth-radius is not available on debian mirrors.
I would like to know what happened to this package and what is the newest way to configure radius auth. Some people have told me to compile this package, but is there not an easier way to do that?
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'. :/
I've recently bought a new computer and installed Windows 7 on it, but left 100GB of space on a separate partition so I could put Debian next to it in dual boot. I have the new Intel i7 950 processor and I run Windows 7 Proffesional 64 bit, so I assumed I had to pick the ia64 debian image. However the CD I burned from the ia64 image didn't boot. (a black screen started and an underscore kept flashing, but nothing else happened)[URL]
I've managed to install i386 Debian on a older intel pentium 4 computer before and that worked fine. I believe I used another application to burn the CD then. This time I've burned the CD with the default Windows CD burn application. I can try burn more CD's but I don't have much left so I want to make sure this is the problem before attempting again. (the burned files on the ia64 CD look exactly the same as the files on the i386 CD, when browsing through the cd files in windows) "If your PC has a 64-bit AMD or Intel processor, you will most likely need the "amd64" images (though "i386" is also fine), the "ia64" images will not work."This seems a bit strange, they recommend me to use the amd64 image if you have a "64-bit AMD or intel processor". I dunno if this is a typo, but it seems weird to me that the AMD-64 Debian version would also work on my Intel machine
In Debian Jessie Gnome with two screens, I would like to execute
xrandr --output HDMI1 --primary --right-of eDP1
xrandr --output eDP1 --rotate left
prior to showing the GNOME user logon screen. Unfortunately, all information I seem to be able to find on this appears to be relevant for pre-systemd Linux only.
The situation is that I have two monitors: One small tilted monitor on the left with 1024 x 768 which should be secondary and one larger landscape monitor on the right with 1920 x 1080 which should be secondary. Everything works persistently AFTER a user has logged on. However, after booting the system or after changing users, the small monitor becomes primary so (a) the user needs to logon using that monitor and (b) as the monitor is physically tilted, one needs to tilt the head to read it wihtout the xrandr commands.
If I can get beyond this issue, there is a second issue: While one can pick the primary and secondary monitor in Gnome, monitor numbers 1 and 2 seem to be fixed. This becomes a problem when using freeRDP to connect to a Windows server with dual monitors. Then, the smaller, secondary monitor is number 1 and thus, it is the Windows logon and primary screen. Is there a way to switch numbers 1 and 2 in Linux, for example somewhere in the grub configuration?
I had to boot into my Windows 7 install on my laptop for the first time in a few months and I noticed that the Windows clock was 4 hours ahead. Windows sync'd its time with the internet, then I booted back into Debian (Lenny) and my clock was now 4 hours behind. Both OS's are set to the same time zone (EDT). The minutes were correct in both systems. Could the fact that EDT is UTC-0400 be relevant?
View 7 Replies View RelatedI recently installed Debian 7 on a dual boot with Windows Vista. Thus, when I boot the computer, I am prompted by a GRUB screen to select Windows Vista loader, Debian, and Debian (recovery mode). I would like to upgrade Windows Vista to Windows 7. Will this cause an issue with GRUB? Will a Windows 7 loader be added to the list or will a Windows 7 loader replace the Windows Vista loader? Will there have to be a setting change within Debian? Within Windows?
View 6 Replies View RelatedI have Windows 10 and Deb 8 dual boot, and I need to re-install Windows but want to avoid (or at least plan for) losing Grub/Linux boot.
Last time I re-installed Windows after Linux I ended up having to re-install Linux again afterwards as well, because I couldn't recover it (seemingly due to complications from encryption). So this time I'm wanting to plan and avoid that.
CURRENT DISK PARTITIONS:
Code: Select allsda1 | 550M | EFI System
sda2 | 128M | Microsoft reserved
sda3 | 175.8G | Microsoft basic data
sda4 | 286M | Linux filesystem (Boot)
sda5 | 28.2G | Linux filesystem (Root)
sda6 | 91.3G | Linux filesystem (Home)
sda7 | 1.9G | Linux swap
[Code] ....
As there is a "Microsoft Reserved" partition and a separate Microsoft directory within the EFI partition, if I just go ahead and reinstall Windows will it install it's boot loader/image to one of it's own partitions? And NOT affect anything else like Grub and other Linux things?
Logic tells me yes, but there seems to be many issues on the internet about installing Windows after Linux.
My primary concern is whatever happens with Windows or anything to do with dual loading etc, is that Linux will still just boot, or I can get it working again without much hassle.
Why is there a reserved Microsoft partition AND a Microsoft directory in the EFI partition? Which one boots Windows?
Why is there a separate Linux Boot partition AND a Linux directory in the EFI partition? Which one boots Linux? Where is Grub invoked from, is one redundant, etc?
How these work. It is possible I've set them up wrong, or with redundant partitions, but both systems have been booting ok for months.
I've been using Debian for a few years but always on dedicated boxes and/or VMs.
Finally decided to dual boot Debian and Windows on my main Desktop PC.
Installed as I normally would using, however this time using a seperate drive (one for the existing Windows 10 install and the other for Debian), Debian install detects that windows has an EFI partition and sticks an entry in there, which is fair enough, and everything working fine. Then I spent some time configuring all my software and set it all up just the way I like it. I've rebooted Debian a few times to check it's working correctly and it is.
The issue arrives when I reboot and load into Windows 10. It boots fine.
However after a further reboot GRUB no longer loads... and the machine just boots directly into Windows 10.
After doing some further digging into my EFI partition (and reinstalling various times) it would appear that after a reboot Windows 10 deletes the entry GRUB creates in my EFI partition after EVERY reboot.
Done some googling and most people advise turning off 'fast boot' in Windows as it locks certain partitions to facilitate the machine going into hibernation, only to find that it's always been turned off on my machine (I recall due to a driver issue with my graphics card this had to be turned off when I installed Windows 10).
I've found this article on the Ubuntu forums : [URL] .... however I've tried their steps and windows is still doing a hostile takeover of my EFI partion after a reboot!
Any way to stop Windows 10 from interfering with my EFI files after a reboot? (without doing the obvious thing and kill Windows off).
I have used dual boot systems using various versions of windows and Debian for many years and have encountered no problems. However, I have a problem with installing Debian on a EeePC (ASUS PC1201) which uses Winows 7. I can not even get started because I can not understand the information that I have on my hard drive partitions. Windows 7 says that I have the following :
Local Disk(C:) 78.1 GB free of 99.9GB
Local Disk(D:) 49.8 GB free of 83.8.GB
NewVolume(G:) 948 KB of 0.99 GB
Local Disk(F:) 37.9 GB free of 38..0 GB
(Originally the ASUS only had two partitions C: and D: I used Gparted to genetate F: and G:)
gparted-live-0.7.1.5 says that I have the following :-
/dev/sda1 ntfs 992.5 KB
/devf/sda2 ntfs 100.00 GB with 66.09GB unused
/dev/sda3 ntfs 132.88GB with 129.88 GB unused
unallocated 1.00 GB
Debian Squeeze (the net install version) will not install. G was the result of trying to provide some swap space. How do I prepare the hard drive so that Squeeze it will install on F: ?
how to install Debian after Windows is already installed. Could someone give me a brief guide to begin the process of installing Windows? When I installed Debian I already made a partition for windows (in the same hard disk), I hope I did it right.
View 3 Replies View RelatedI've a Lenovo G50-80T with W8.1. I want to install Debian 8.1 in dualbooting mode. I've done this other times without problems. But this time I want encrypt the Linux partition (not the Windows partition). I'll use dm-crypt to do that. I want to know if this way is secure for protect the data on Linux partition or if I need encrypt the entire drive.
View 3 Replies View RelatedI'm currently dual-booting Squeeze & Windows XP on a machine i use frequently.
In my experience on the desktop, i now see no reason to have Windows XP as a boot option, & wanted to try & avoid a full re-installation of Debian in order to remove XP (merging it's partition with / ).
I have a checklist that i put together, but wanted to be sure this was all correct before going forward.
1. Perform full back-up of all data.
2. Boot into Debian, through GUI -
System Tools > Disk Utility
- Select HDD (80GB Hard Disk)
- Select windows partition ( /dev/sda1 )
- Format /dev/sda1 to Ext4 Filsystem
3. Boot Live CD
- Use gParted to extend /dev/sda2 (was 38GB, will extend to 78GB)
4. Remove XP from the boot menu.
( Note: My ~ folder is on the same physical drive as / (same volume), but i actually store all Media on a separate physical drive which is formatted in NTFS. I plan on reinstalling XP using a virtual hard disk, & sharing that with the virtual machine.Here is a screenshot of my Disk Utility - [URL]
me a easy and right answer to this post
View 3 Replies View Relatedis it safe to install a dual boot windows 32bit and a linux 64bit on the same pc?
View 14 Replies View RelatedThis problem goes back to when I first purchased my laptop 4 years ago: Dell Precision M90. It came with Vista, but I wanted Ubuntu on instead. In order to get bluetooth to work, I had to downgrade the firmware. This is all fine and means bluetooth works in XP too. However, now, I have a dual boot with Windows 7 and Squeeze, I use Vista drivers (as Dell don't provide 7 drivers) and this has upgraded the firmware, and broken bluetooth in Squeeze. How can I get bluetooth working in both Squeeze and Windows 7? Could changing the hardware help? If so, what to?
View 2 Replies View RelatedAfter 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?
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?
View 2 Replies View RelatedI recently decided to buy a new pc and install only one operating system: Debian.
The PC has an Intel Core 2 Duo, 4GB of RAM and installed Linux 3.16.0-4-amd64 with desktop KDE SC 4.14.2
I can use it for a while, but it always ends with the same problem: All the windows turn black, except the edge.
Furthermore, in the application launcher menu, the edge only appears, like when I make right click on the desktop.
They appear completely transparent. Only be solved by restarting the PC.
I recently installed GNOME on my debian machine. I want to try using that as a second monitor for my windows 8 computer. I can't seem to find instructions on google, I want to try doing this wirelessy; is there freeware that lets me do this?
View 3 Replies View RelatedHow 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 RelatedThe 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 ?
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.
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.
View 8 Replies View RelatedWith "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?
I 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 RelatedWhen 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 RelatedI downloaded Ubuntu 10.04 and I want to make a dual boot with Windows 7 Ultimate using Windows Boot Manager...
I deleted my last Ubuntu OS (9.10) just because of GRUB
There seems to be no documentation on how to automount partitions and USB devices under systemd in Jessie. (Overall, systemd entirely lacks any useful documentation or GUI configuration tools -- all very cryptic and hidden.)
I created custom files to enable automounting. I put them in /etc/systemd/system -- this may not be the right place, but it works.
Kernel note:
This does not work under the old Wheezy kernel linux-image-3.2.0-4.
To automount my Windows partition so I can access its files, I created:
/etc/systemd/system/media-windows.mount
The name of the file must match the mount point -- in this case, /media/windows
My file notes the device and file type, plus an fmask option so all the Windows files don't seem to be executable:
[Unit]
Description = windows mount to /media/windows
[Mount]
What=/dev/sda1
Where=/media/windows
Type=ntfs-3g
Options=fmask=111
[Install]
WantedBy=multi-user.target
The file ownership must be root.root. Apparently it doesn't need to be executable.
After creating, enable with:
sudo systemctl enable media-windows.mount
and it will mount on the next boot.
I read elsewhere that the before running the enable command you should run a start command:
sudo systemctl start media-windows.mount
but that didn't work for me.