jhutchins_wk 2017-03-03 09:47:18
You could also try mpv.
Piraty 2017-03-03 09:49:22
simple dd command doesn't make a bootable usb stick for me, what am i missing? (other distro's live mediums work fine on the same machine)
somiaj 2017-03-03 09:49:32
jhutchins_wk: they said mplayer and mpv didn't work, which doens't surprise me since it is a video driver problem.
Piraty 2017-03-03 09:49:41
using debian 8.7 xfce-live
somiaj 2017-03-03 09:49:41
Piraty: give us the exact command you typed.
Piraty 2017-03-03 09:49:52
sudo dd bs=4M if=debian-live-8.7.1-amd64-xfce-desktop.iso of=/dev/sdc status=progress ; sync
somiaj 2017-03-03 09:51:05
Piraty: that should work just fine, does your system support or is configured to do legacy boot?
somiaj 2017-03-03 09:51:21
Piraty: if intsalling debian you shouldn't use the live images, and the live images only do legacy boot, not uefi.
Piraty 2017-03-03 09:51:47
somiaj: legacy is enabled.
jhutchins_wk 2017-03-03 09:51:56
Piraty: check the md5sum of the file.
Piraty 2017-03-03 09:55:50
but that is the idea of the live system. i want to check if the errors i have with other distros do persist
Piraty 2017-03-03 09:55:57
namely hardware issue with amdgpu
jhutchins_wk 2017-03-03 09:57:27
Piraty: check the md5sum of the iso file.
dannyLopez 2017-03-03 09:57:37
Any can help whit a program inside Debian?
jhutchins_wk 2017-03-03 09:58:00
Piraty: The graphics should not be affected if you boot in CMOS mode vs. EFI.
Piraty 2017-03-03 09:58:25
checksum is ok
jhutchins_wk 2017-03-03 09:58:27
dannyLopez: Only if you tell us clearly what the problem is.
Piraty 2017-03-03 09:58:55
jhutchins_wk: it may be affected due to firmware issues i found regarding same errors
jhutchins_wk 2017-03-03 09:59:05
Piraty: Well, that's one thing eliminated. Can you boot to the stick on another system?
dannyLopez 2017-03-03 09:59:40
The thing is I have a Nextcloud server, and I install Owncloud client to connect, in all Ubuntu system works fine, but in my Debian system dont connect, say "The credential is bad"
Piraty 2017-03-03 10:00:33
jhutchins_wk: have nothing else to try sorry. other distros work right away, dd is the same command
Piraty 2017-03-03 10:00:34
jhutchins_wk: despite the machine im sitting on now, but that is impossible to shutdown right now
a___ 2017-03-03 10:00:57
I installed debian on two hard drives. I swap the drives physically. On one drive, I can select 'debian' in the BIOS settings and it will boot. In the other, 'debian' is not a choice and debian fails to boot. Why?
a___ 2017-03-03 10:01:37
(i.e. I select 'debian' in the BIOS settings boot menu)
mtn 2017-03-03 10:01:41
a___: because grub is not installed on that drive
a___ 2017-03-03 10:02:27
mtn: it is installed. After I installed debian on the drive, it worked. When I switched to the other hard drive then switched back, it no longer worked. But I can still boot debian on other hard drive. It's strange...
mtn 2017-03-03 10:02:59
a___: I will bet grub is only installed on the drive that works and that drive usually boots first
a___ 2017-03-03 10:05:15
mtn: what I mean is I installed debian on one of the drives and it booted using GRUB. when I switch drives then switch back it no longer boots. It just says 'insert media'. If I go in BIOS and change the order to select the hard drive it still doesn't work. On the drive that DOES work, 'debian' appears in the BIOS boot menu (I mean the BIOS menu, NOT the grub menu). I don't understand - I don't see how 'debian' can appear in the BIOS, I t
a___ 2017-03-03 10:05:15
hought that would only appear in the GRUB menu...
a___ 2017-03-03 10:05:51
and grub IS installed on both drives - when the first one worked, it loaded the GRUB menu straight away
mtn 2017-03-03 10:06:03
a___: grub is installed on a hard drive, so if that drive is being booted, it shows grub. if that drive is not being booted, no grub
mtn 2017-03-03 10:06:29
a___: ok. if it is installed on both, I have no idea
a___ 2017-03-03 10:07:07
ok, yep the GRUB menu appeared on the first one, but when I switched drives then switched back, it didn't boot anymore. confusing..
a___ 2017-03-03 10:07:46
anyone?
jhutchins_wk 2017-03-03 10:08:48
a___: When you switch the order in which the BIOS sees the drives, you are probably changing the effective name of each drive (sda, sdb). You might be able to fix it by changing all drive references to UUIDs.
a___ 2017-03-03 10:09:56
ok. how do I do that?
ompaul 2017-03-03 10:10:31
1uuid
ompaul 2017-03-03 10:10:35
!uuid
dpkg 2017-03-03 10:10:35
A Universally Unique IDentifier (UUID) is used to reference disk partitions (among other things). See currently known partition UUIDs with 'blkid'. In /etc/fstab, use "UUID=dead-beef-0420-etc" as the partition name. UUIDs help to cope with device name changes such as hda->sda ( transition) or changes in USB disk order discovery. tools accept PV/VG/LV UUIDs as arguments, use {pv,vg,lv}display to acquire.
a___ 2017-03-03 10:12:44
Ok. Does that mean GRUB is set to boot a particular drive name (sda, sdb), and by changing the bios boot order I changed those names, so GRUB fails to load the drive. Is that right?
icez 2017-03-03 10:14:02
a___: no, but uuid's are better
jhutchins_wk 2017-03-03 10:15:01
a___: That's my guess about what may be happening.
jhutchins_wk 2017-03-03 10:15:28
a___: There's no standard way for a BIOS to change boot drives.
a___ 2017-03-03 10:16:33
jhutchins_wk: ok, thanks for your help.
jhutchins_wk 2017-03-03 10:18:07
a___: Hope it helps.
Shadow_7 2017-03-03 10:18:20
except by removing all drives except the one you wish to boot
a___ 2017-03-03 10:19:02
Shadow_7: I am unplugging one drive and plugging in another. So only one drive is used at a time.
mtn 2017-03-03 10:19:23
which is why I said grub was missing
Shadow_7 2017-03-03 10:19:23
although lots of boards have soldered on drives these days
c-c 2017-03-03 10:21:59
I wish people would only buy laptops with socketed cpu's
c-c 2017-03-03 10:22:12
that would be awesome
c-c 2017-03-03 10:22:24
upgrade that lapper 4 years later
c-c 2017-03-03 10:22:41
but alas, dumb consumer horde
seglaf 2017-03-03 10:22:54
First time installing Debian on a remote virtual host, getting a failed installation: "The failing step is: Install the system"
a___ 2017-03-03 10:22:57
why does 'debian' appear as an option in the BIOS for one of the drives? I thought it would just show generic hard drive, CD drive, etc
seglaf 2017-03-03 10:23:03
What would be the best way to troubleshoot this?
c-c 2017-03-03 10:23:17
seglaf: so that appears, when
seglaf 2017-03-03 10:23:25
Installing from the iso
c-c 2017-03-03 10:23:35
and, that appears, when?
mtn 2017-03-03 10:23:53
a___: silly question: where did you install grub on the non-booting drive?
a___ 2017-03-03 10:24:30
mtn: don't know, just did a standard debian install from DVD 1, it installed grub automatically
a___ 2017-03-03 10:24:40
mtn: first time installing debian
c-c 2017-03-03 10:24:45
a___: perhaps the volume label or identifier is now 'debian' for some reason
mtn 2017-03-03 10:24:47
a___: is your machine legacy or efi boot?
a___ 2017-03-03 10:25:07
mtn: hold on..
seglaf 2017-03-03 10:25:30
c-c: after the partitioning of the harddrive and during the "Install the System" phase
a___ 2017-03-03 10:26:16
mtn: ASRock H81M-HDS
mtn 2017-03-03 10:26:38
a___: oh, but is it set for legacy or efi boot in the setup?
c-c 2017-03-03 10:26:38
seglaf is there anything in /var/log of the target partition?
a___ 2017-03-03 10:27:11
mtn: I'll check and return, hold on
seglaf 2017-03-03 10:27:56
c-c: I don't think there is even a /var/log yet as nothing has ever been installed on this server
c-c 2017-03-03 10:28:14
seglaf: know, or think? I only care about the former
seglaf 2017-03-03 10:28:17
c-c: its being virtually hosted on the server, forgot to mention
seglaf 2017-03-03 10:28:29
c-c: sure thing one sec
seglaf 2017-03-03 10:28:50
c-c: know
c-c 2017-03-03 10:29:24
seglaf: ok, so did you check the install image checksums before install?
seglaf 2017-03-03 10:29:54
c-c: no I did not
c-c 2017-03-03 10:30:13
do that - ensure not corrupt install image, or just re-download
a___ 2017-03-03 10:34:17
mtn: couldn't find anything about efi/legacy, but it mentions uefi a few times. what is the significance?
jhutchins_wk 2017-03-03 10:34:30
!uefi
dpkg 2017-03-03 10:34:31
Unified Extensible Firmware Interface (UEFI) is a firmware interface specification, intended to replace the firmware interface. Debian 7 "Wheezy" and later releases support installation in (U)EFI mode on 64-bit PC systems (amd64), is currently not supported. http://www.uefi.org/
mtn 2017-03-03 10:34:52
a___: if you are doing a efi boot, then you have to have an efi partition on the drive. is there one on the non-booting drive?
jhutchins_wk 2017-03-03 10:34:58
EFI is an earlier version/designation, it's close enough to the same.
mtn 2017-03-03 10:35:23
a___: if no efi partition, no grub :)
a___ 2017-03-03 10:35:34
mtn: Ok. I will have to check. That may be the problem then. Thanks for the help :)
jhutchins_wk 2017-03-03 10:35:39
a___: People often just use efi for uefi, shorter.
a___ 2017-03-03 10:35:48
ok
mtn 2017-03-03 10:36:13
jhutchins_wk: some of us don't know any better :P
jhutchins_wk 2017-03-03 10:36:44
iirc macs and ibm mainframes use actual efi.
a___ 2017-03-03 10:37:20
mtn: assuming efi partition is missing on the non-booting device, can I just disable efi boot in the BIOS?
jhutchins_wk 2017-03-03 10:37:43
a___: That would be one way to solve it, if that's the problem.
a___ 2017-03-03 10:38:04
ok, thanks
jhutchins_wk 2017-03-03 10:38:08
a___: I don't know that the drives would have a fallback bootloader though. YOu might need to install non-efi grub.
jhutchins_wk 2017-03-03 10:40:04
If it's an EFI system, a boot record for debian would get written to the efi partition. I have the option to use either the Windows bootloader or the Debian bootloader (which doesn't work for graphics reasons).
jhutchins_wk 2017-03-03 10:40:21
That's a project for this weekend
RFleming 2017-03-03 10:40:45
Can the efi boot manager handle multiple bootable devices?
RFleming 2017-03-03 10:41:09
or do you still need something else to dual-boot?
RFleming 2017-03-03 10:41:39
say Disk A has an EFI boot partition for Windows, and Disk B has an EFI partition for Linux
RFleming 2017-03-03 10:41:54
can the boot manager boot either-or, or does it do funky things?
RFleming 2017-03-03 10:43:13
or is that only needed when it's the same disk, but different partitions?
mtn 2017-03-03 10:43:38
RFleming: one efi partition can handle dual boot. efi on each drive will still work if you use the boot menu, not the grub menu
RFleming 2017-03-03 10:44:10
the 'select your boot device' menu? F9 or F12
RFleming 2017-03-03 10:44:22
My HP uses F9, my Lenovo's F12
mtn 2017-03-03 10:44:34
RFleming: yes, that one
RFleming 2017-03-03 10:44:58
I thought I'd ask, because I installed Debian on my HP, and debian-installer warned me about multiple EFI boot records
RFleming 2017-03-03 10:45:07
suggested using a non-efi one.
