On 9/16/24 03:32, Anssi Saari wrote:
Will Mengarini writes:
ViewSonic 15E
Isn't that a CRT from the '90s? So you have some adapter for HDMI? Is
there really no other monitor you could use?
I tried using a search engine and came up empty:
https://html.duckduckgo.com/html?q=site%3AViewSon
On Sun 15 Sep 2024 at 23:45:42 (-0700), Will Mengarini wrote:
> Felix Miata [24-09/15=Sun 22:01 -0400]:
> > F12 should get you the Gigabyte BBS menu.
>
> Something happens when I press , but I can't
> tell what, because I can't read the screen, because
> it is out of sync, using an unsupported re
Will Mengarini writes:
> ViewSonic 15E
Isn't that a CRT from the '90s? So you have some adapter for HDMI? Is
there really no other monitor you could use?
On 16.09.2024 04:12, Will Mengarini wrote:
I am trying to install Debian on a new prebuilt, but when I
boot and press , the screen is garbled. Windows later
figures it out, but by that time it's too late to tell the
BIOS to boot from a USB stick on which I've installed netinst.
The mobo is a Gi
On Sun, 15 Sep 2024 23:28:36 -0700
Will Mengarini wrote:
> * Charles Curley [24-09/15=Sun
> 18:15 -0600]:
> > On Sun, 15 Sep 2024 16:12:45 -0700
> > Will Mengarini wrote:
> >
> > > I am trying to install Debian on a new prebuilt, but when I
> > > boot and press , the screen is garbled.
> >
* Felix Miata [24-09/15=Sun 22:01 -0400]:
> Will Mengarini composed on 2024-09-15 16:12 (UTC-0700):
>
> > I am trying to install Debian on a new prebuilt, but when I
> > boot and press , the screen is garbled. Windows later
> > figures it out, but by that time it's too late to tell the
> > BIOS t
* Charles Curley [24-09/15=Sun 18:15 -0600]:
> On Sun, 15 Sep 2024 16:12:45 -0700
> Will Mengarini wrote:
>
> > I am trying to install Debian on a new prebuilt, but when I
> > boot and press , the screen is garbled.
>
> Slow down. When you boot what? A Debian installation (which,
> presumably, ap
* David Christensen [24-09/15=Sun 17:13 -0700]:
> On 9/15/24 16:12, Will Mengarini wrote:
> > I am trying to install Debian on a new prebuilt, but when I
> > boot and press , the screen is garbled. Windows later
> > figures it out, but by that time it's too late to tell the
> > BIOS to boot from
Will Mengarini composed on 2024-09-15 16:12 (UTC-0700):
> I am trying to install Debian on a new prebuilt, but when I
> boot and press , the screen is garbled. Windows later
> figures it out, but by that time it's too late to tell the
> BIOS to boot from a USB stick on which I've installed netins
On Sun, 15 Sep 2024 16:12:45 -0700
Will Mengarini wrote:
> I am trying to install Debian on a new prebuilt, but when I
> boot and press , the screen is garbled.
Slow down. When you boot what? A Debian installation (which,
presumably, appeared to be successful), or a Debian installer? If the
latt
On 9/15/24 16:12, Will Mengarini wrote:
I am trying to install Debian on a new prebuilt, but when I
boot and press , the screen is garbled. Windows later
figures it out, but by that time it's too late to tell the
BIOS to boot from a USB stick on which I've installed netinst.
The mobo is a Gigab
On Thu, Jun 08, 2023 at 10:09:47PM +0100, Mick Ab wrote:
> Is there a command that can be used to determine the BIOS version being
> used on the motherboard.
>
> I have used dmidecode,
OKay
> but at the bottom of the man page for dmidecode there is :-
>
> "More often than not, information conta
Mick Ab wrote:
> Is there a command that can be used to determine the BIOS version being
> used on the motherboard.
>
> I have used dmidecode, but at the bottom of the man page for dmidecode
> there is :-
>
> "More often than not, information contained in the DMI tables is
> inaccurate, incomple
On Fri, 24 Feb 2023, Keith Bainbridge wrote:
Remember too that many distros have activated a grub setting that means it will
no longer search for other installations. Turn that off:
Edit the file in /etc/default named 'grub'. Add 'GRUB_DISABLE_OS_PROBER=false'
anywhere in the script. Run grub
Remember too that many distros have activated a grub setting that means it will
no longer search for other installations. Turn that off:
Edit the file in /etc/default named 'grub'. Add 'GRUB_DISABLE_OS_PROBER=false'
anywhere in the script. Run grub install, 'grub-install'
--
All the best
On Thu, Feb 23, 2023 at 12:49:25PM +, Simeone Dominique wrote:
> Good afternoon,
> i installed a linŭx deepin operating system in addition to debian and linŭx
> mint and when i start the fujitsu it boots to the bios as if there is no
> operating system.
> What to do?
> Good for you.
> Mr. Dom
On Sb, 08 aug 20, 14:38:30, Andrew Cater wrote:
>
> dpkg-reconfigure -plow tzdata
>
> [That's the dpkg-reconfigure command, -plow to force asking low priority
> questions rather than taking the default answers, and tzdata being the file
> that sets the timezone.]
As the manpage states, dpkg-reco
Hi Albretch,
If I'm reading your question correctly:
Why can't you set the locale for one country, the timezone for a second,
the keyboard for a third?
You can. As root or equivalent, you can reset timezone with
dpkg-reconfigure -plow tzdata
[That's the dpkg-reconfigure command, -plow to force
On the installer it says:
Configure clock: if the desired time zone is not listed ...
Select your time zone:
https://manjaro.site/step-by-step-install-debian-9-0-netinstall-version/install-debian-9-0-configure-clock/
but why can't you set up your computer as US English and be, say, in
the
On Fri, Jul 31, 2020 at 01:56:10PM +0200, Albretch Mueller wrote:
> OK, I will studz and try the manz options you have explain to me.
>
> > Your posts are sometimes nearly... whimsical.
>
> Many of you have tell me such things, "you should know that ... "
> "why do you even ask if it is so easz
OK, I will studz and try the manz options you have explain to me.
> Your posts are sometimes nearly... whimsical.
Many of you have tell me such things, "you should know that ... "
"why do you even ask if it is so easz to find the answer on the
Internet?" ...
Posts are not "whimsical" per se,
On Fri, 31 Jul 2020 08:55:22 +0300
Andrei POPESCU wrote:
Hello Andrei,
>What difference does it make for a signature like his ("-- t")?
It doesn't work.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
Give me a reason for liv
On Jo, 30 iul 20, 17:13:18, Brad Rogers wrote:
> On Thu, 30 Jul 2020 17:58:10 +0200
> wrote:
>
> Hello to...@tuxteam.de,
>
> *PLEASE* fix your sig separator.
What difference does it make for a signature like his ("-- t")?
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
sig
On Thu, 30 Jul 2020 17:58:10 +0200
wrote:
Hello to...@tuxteam.de,
*PLEASE* fix your sig separator.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
Go away, come back, go away, come back
Leave Me Alone (I'm Lonely) - P!nk
pgp
On Thu, Jul 30, 2020 at 03:50:54PM +0100, Brad Rogers wrote:
> On Thu, 30 Jul 2020 17:08:19 +0300
> Anssi Saari wrote:
>
> Hello Anssi,
>
> >Since Windows 7 it's possible to tell Windows that RTC is UTC. IMO,
> >setting RTC to UTC time is the right thing to do, messing around with
>
> Good to k
On Thu, 30 Jul 2020 17:08:19 +0300
Anssi Saari wrote:
Hello Anssi,
>Since Windows 7 it's possible to tell Windows that RTC is UTC. IMO,
>setting RTC to UTC time is the right thing to do, messing around with
Good to know(1). O/P doesn't state which version of Windows they're
using, so I'll make
On Thu, Jul 30, 2020 at 05:08:19PM +0300, Anssi Saari wrote:
[...]
> Since Windows 7 it's possible to tell Windows that RTC is UTC.
Wow. They got it right. I'm dumbfounded.
>IMO,
> setting RTC to UTC time is the right thing to do,
Brad Rogers writes:
> On Thu, 30 Jul 2020 07:19:12 -0400
> Albretch Mueller wrote:
>
> Hello Albretch,
>
>> How do you make Linux get the time from the BIOS at start time and
>>take it from there?
>
> Linux *is* reading the RTC; The problem is that Windows expects that
> time to be in the local
On Thu, Jul 30, 2020 at 07:19:12AM -0400, Albretch Mueller wrote:
> I used the same laptop with another hard drive with a Windows
> installation which shows the time correctly.
>
> How do you make Linux get the time from the BIOS at start time and
> take it from there?
Your posts are sometimes
On Thu, 30 Jul 2020 07:19:12 -0400
Albretch Mueller wrote:
Hello Albretch,
> How do you make Linux get the time from the BIOS at start time and
>take it from there?
Linux *is* reading the RTC; The problem is that Windows expects that
time to be in the local time zone, and sets it so, rather th
On 7/30/20, Albretch Mueller wrote:
> I used the same laptop with another hard drive with a Windows
> installation which shows the time correctly.
>
> How do you make Linux get the time from the BIOS at start time and
> take it from there?
While you're waiting for others to chime in, this is w
hwclock --hctosys will do it - run a batch file?
Or have ntpdate run automatically as the system boots?
If you mean that Debian shows a different time to Windows consistently -
check that one OS isn't resetting the other's clock. You can persuade
Windows _not_ to reset the clock on daylight savin
On Wed, 21 Feb 2018 23:19:04 +0100
Pascal Hambourg wrote:
> Le 21/02/2018 à 03:53, Dan Norton a écrit :
> >
> > In contrast, with GPT and LVM, for the second and subsequent
> > installations, the partitioning and defining of PVs, VGs, and LVs
> > needs to be done before installation using gdisk
Le 21/02/2018 à 03:53, Dan Norton a écrit :
In contrast, with GPT and LVM, for the second and subsequent
installations, the partitioning and defining of PVs, VGs, and LVs needs
to be done before installation using gdisk and the LVM tools in /sbin.
Then, the installer with manual partitioning can
As the OP, I want to try to clear up some of the confusion. I have
caused plenty of it. :-)
I drop-kicked the partitions I had set up and started over with a bare
(nothing but free space) sda block device. At some point I have
expressed doubt that my PC could handle UEFI correctly. This is not
tru
Hi.
On Sat, Dec 30, 2017 at 01:54:00PM -, sejobu...@bitmessage.de wrote:
> i have an option in my new pc/bios : vt virtualization
> does it help the pc to work 'better' or is it used only when i run a vm ?
To my best knowledge, only virtualization software is using it.
> i have an op
Le 07/12/2017 à 00:03, Felix Miata a écrit :
In the context of a GPT partitioned disk,
That context was missing from post you're complaining about.
That was your post, and it had plenty enough context :
- BIOS boot partition only exists in GPT
- type EE is used in GPT protective MBR
Anyw
On 12/05/17 15:18, Pascal Hambourg wrote:
Le 05/12/2017 à 06:55, David Christensen a écrit :
4. The firmware finds the first GPT partition and file system, which
look "right" for EFI boot images.
No.
5. The firmware reads this file system and finds only one file, which
it loads and runs (s
Pascal Hambourg composed on 2017-12-06 23:16 (UTC+0100):
> Felix Miata composed:
>> Nothing in that post makes it unambiguous that an MBR (MSDOS) partitioned
>> disk
>> was not the subject of discussion.
> In the context of a GPT partitioned disk,
That context w
Le 05/12/2017 à 03:33, Felix Miata a écrit :
Pascal Hambourg composed on 2017-12-05 00:41 (UTC+0100):
You're the only one bringing additional confusion.
Nobody but you talked about doing such a stupid thing as removing a type
ee partition. Dan and I only talked about removing the BIOS boot
part
Le 05/12/2017 à 06:55, David Christensen a écrit :
I wiped the SSD, ran d-i, and chose "Partitioning method" -> "Guided -
use entire disk and set up encrypted LVM", which produced:
LVM VG debian-vg, LV home - 3.5 GB Linux device-mapper (linear)
#1 3.5 GB f ext4
On Mon 04 Dec 2017 at 17:34:52 (-0800), David Christensen wrote:
> On 12/04/17 07:21, David Wright wrote:
> >I recently reformatted a disk thus:
> >
> >puck: GPT-style, master
> >
> >Part # filesys sizecoderôle
> >puck- 1007KiB partition tabl
On 12/04/2017 12:17 AM, David Christensen wrote:
On 12/03/17 13:44, Dan Norton wrote:
On 12/02/2017 02:35 PM, David Christensen wrote:
I'm not making progress with this PC so I'll probably abandon GPT.
The disk is 1T and it was handled by the extended partition scheme
before this experiment an
On 12/04/17 17:34, David Christensen wrote:
That's why I plan to try again with the simplest automagic partitioning
and see what happens.
I wiped the SSD, ran d-i, and chose "Partitioning method" -> "Guided -
use entire disk and set up encrypted LVM", which produced:
LVM VG debian-vg
Pascal Hambourg composed on 2017-12-05 00:41 (UTC+0100):
> You're the only one bringing additional confusion.
> Nobody but you talked about doing such a stupid thing as removing a type
> ee partition. Dan and I only talked about removing the BIOS boot
> partition sda1.
In https://lists.debian.
On 12/04/17 07:21, David Wright wrote:
I recently reformatted a disk thus:
puck: GPT-style, master
Part # filesys sizecoderôle
puck- 1007KiB partition tables and alignment space
puck01 - 3MiBEF02bios-boot for Grub (bios
On 12/04/17 06:39, Dan Norton wrote:
On 12/04/2017 12:27 AM, David Christensen wrote:
Are there any other commands that readers might find interesting
(before I wipe the SSD)?
Just out of curiosity, lvdisplay?
# lvm lvdisplay
--- Logical volume ---
LV Path/dev/vg-stretch/
Le 04/12/2017 à 00:40, Felix Miata a écrit :
Pascal Hambourg composed on 2017-12-03 23:40 (UTC+0100):
...
Then, to proceed, remove /dev/sda1 partition followed by grub-install?
Removing the partition won't help. It is just useless, it does not harm.
If sda1 is a type EEh partition, doin
On Sun 03 Dec 2017 at 21:27:20 (-0800), David Christensen wrote:
> On 12/03/17 21:17, David Christensen wrote:
> >But, it was not a total loss -- I can now dissect the SSD.
>
> More info:
>
> # lsblk /dev/sda
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:00 14.9G 0 disk
> |-sda1
On 12/04/2017 12:27 AM, David Christensen wrote:
On 12/03/17 21:17, David Christensen wrote:
But, it was not a total loss -- I can now dissect the SSD.
More info:
# lsblk /dev/sda
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 14.9G 0 disk
|-sda1 8:1 0 953M 0 part
`-sda2
On 12/03/17 21:17, David Christensen wrote:
But, it was not a total loss -- I can now dissect the SSD.
More info:
# lsblk /dev/sda
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 14.9G 0 disk
|-sda1 8:10 953M 0 part
`-sda2 8:20 4.7G 0 part
# parted /dev/sda u s p
On 12/03/17 13:44, Dan Norton wrote:
On 12/02/2017 02:35 PM, David Christensen wrote:
I'm not making progress with this PC so I'll probably abandon GPT. The
disk is 1T and it was handled by the extended partition scheme before
this experiment and it probably can again. I still want to do LVM an
On 12/02/2017 02:35 PM, David Christensen wrote:
[...]
Where is /boot?
Possibly, this is a better answer:
$ df -Th
Filesystem Type Size Used Avail Use% Mounted on
[...]
/dev/sda1 vfat 992K 855K 138K 87% /boot/efi
/dev/mapper/debian8--vg-tmp
Pascal Hambourg composed on 2017-12-03 23:40 (UTC+0100):
...
>>> Then, to proceed, remove /dev/sda1 partition followed by grub-install?
> Removing the partition won't help. It is just useless, it does not harm.
>> If sda1 is a type EEh partition, doing that will probably dig your hole too
>> d
On 12/03/2017 02:04 PM, Felix Miata wrote:
Dan Norton composed on 2017-12-04 08:00 (UTC-0500):
Felix Miata wrote:
Dan Norton composed on 2017-12-03 16:44 (UTC-0500):
Note the above is currently from the future. Apparently the PC you are emailing
from is advanced one day.
Must be a result of m
Le 03/12/2017 à 22:51, Felix Miata a écrit :
Dan Norton composed on 2017-12-03 15:54 (UTC-0500):
Pascal Hambourg wrote:
Dan Norton composed:
Yes, no grub in mbr - unless installer insists.
Then what you wrote earlier was wrong : GRUB is not installed in
/dev/sda1, and this partition is
Dan Norton composed on 2017-12-03 15:54 (UTC-0500):
> Pascal Hambourg wrote:
>> Dan Norton composed:
>>> Yes, no grub in mbr - unless installer insists.
>> Then what you wrote earlier was wrong : GRUB is not installed in
>> /dev/sda1, and this partition is useless. As I wrote earlier, a BIOS
On 12/03/2017 02:16 PM, Pascal Hambourg wrote:
Le 04/12/2017 à 13:32, Dan Norton a écrit :
On 12/03/2017 06:49 AM, Felix Miata wrote:
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
Felix Miata composed:
...
So I guess that the OP means that the core image of GRUB is in
sda1, an
On 12/03/2017 01:04 PM, Felix Miata wrote:
Dan Norton composed on 2017-12-04 07:32 (UTC-0500):
Note your posts are still coming from the future. Today ATM in zone -0500 it
is
still the 3rd of December.
Felix Miata wrote:
I'm pretty sure that was not OP's intent, i.e., none of Grub at all i
Le 04/12/2017 à 13:32, Dan Norton a écrit :
On 12/03/2017 06:49 AM, Felix Miata wrote:
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
Felix Miata composed:
...
So I guess that the OP means that the core image of GRUB is in sda1, and
the boot image of GRUB is in the MBR of sda.
(.
Dan Norton composed on 2017-12-04 07:32 (UTC-0500):
Note your posts are still coming from the future. Today ATM in zone -0500 it is
still the 3rd of December.
> Felix Miata wrote:
>> I'm pretty sure that was not OP's intent, i.e., none of Grub at all in MBR.
> Yes, no grub in mbr - unless inst
On 12/03/2017 06:49 AM, Felix Miata wrote:
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
Felix Miata composed:
...
So I guess that the OP means that the core image of GRUB is in sda1, and
the boot image of GRUB is in the MBR of sda.
Based on OP's response to
https://lists.debi
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
> Felix Miata composed:
...
> So I guess that the OP means that the core image of GRUB is in sda1, and
> the boot image of GRUB is in the MBR of sda.
Based on OP's response to
https://lists.debian.org/debian-user/2017/11/msg00563.html
i
Le 02/12/2017 à 05:07, Dan Norton a écrit :
On 12/01/2017 08:54 PM, David Christensen wrote:
>
> # fdisk -t dos /dev/sda
Your original post indicated a GPT partition table. Forcing an MS-DOS
MBR partition type means the tool will be looking at fake information
that your GPT formatting tool
Le 03/12/2017 à 00:09, Felix Miata a écrit :
Michael Lange composed on 2017-12-02 22:33 (UTC+0100):
On Fri, 1 Dec 2017 23:07:15 -0500 Dan Norton wrote:
(...)
What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
where?
GRUB2 to sda1.
I did not read this thread in detail,
Michael Lange wrote:
> Windows is a pain in the neck of
> course, still booting a Live system and reinstalling grub from a chroot
> environment seems comparatively easy to me compared to the OP's
> troubles ;)
Agreed here and this is exactly what I do.
+ grub2 finds windows automatically and perh
On 12/02/2017 02:35 PM, David Christensen wrote:
On 12/01/17 20:07, Dan Norton wrote:
On 12/01/2017 08:54 PM, David Christensen wrote:
On 12/01/17 10:50, Dan Norton wrote: >>> Maybe this is the wrong
forum, but please bear with me a little bit.
This post was sent from a desktop with jessie inst
On Sat, 2 Dec 2017 18:09:56 -0500
Felix Miata wrote:
> Michael Lange composed on 2017-12-02 22:33 (UTC+0100):
>
> > On Fri, 1 Dec 2017 23:07:15 -0500 Dan Norton wrote:
>
> > (...)
> >> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
> >> > where?
>
> >> GRUB2 to sda1.
>
>
Michael Lange composed on 2017-12-02 22:33 (UTC+0100):
> On Fri, 1 Dec 2017 23:07:15 -0500 Dan Norton wrote:
> (...)
>> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
>> > where?
>> GRUB2 to sda1.
> I did not read this thread in detail, so maybe this has already been
> dis
On Fri, 1 Dec 2017 23:07:15 -0500
Dan Norton wrote:
(...)
> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
> > where?
> >
>
>
> GRUB2 to sda1.
>
I did not read this thread in detail, so maybe this has already been
discussed, but I have just now been thinking, shouldn't g
On 12/01/17 20:07, Dan Norton wrote:
On 12/01/2017 08:54 PM, David Christensen wrote:
On 12/01/17 10:50, Dan Norton wrote: >>> Maybe this is the wrong forum, but
please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem
is it will not boot normally.
Hi,
Dan Norton wrote:
> OK, the syslinux and syslinux-efi packages are now installed
SYSLINUX and GRUB are competitors (with GRUB winning the race on hard disk
but lagging behind on ISO 9660 for old BIOS).
I mentioned the SYSLINUX file "mbr.bin" (source: mbr.S) only to
substantiate my statement a
On 12/01/2017 02:58 PM, Thomas Schmitt wrote:
Hi,
Dan Norton wrote:
# fdisk -l
...
Disklabel type: gpt
In the dim past, fdisk
could set a partition as "active", which was its euphemism for "bootable".
I guess, this applies only to MBR partition tables, not to GPT as on your
disk.
As Pascal st
On 12/01/2017 08:54 PM, David Christensen wrote:
On 12/01/17 10:50, Dan Norton wrote:
Maybe this is the wrong forum, but please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem
is it will not boot normally. Network booting has been disabled in
th
On 12/01/17 10:50, Dan Norton wrote:
Maybe this is the wrong forum, but please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem is
it will not boot normally. Network booting has been disabled in the
NVRAM setup. After POST there is a one-liner whic
Dan Norton composed on 2017-12-01 16:23 (UTC-0500):
> The PC is simply not seeing the 1T sda, which is the only disk. It's not
> even getting as far as the mbr/grub. The PC appears to be no more than 5
> years old, based on the BIOS date, but it may be old enough to have a
> flaky UEFI. Should
On 12/01/2017 02:29 PM, Pascal Hambourg wrote:
Le 01/12/2017 à 19:57, Greg Wooledge a écrit :
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
Disklabel type: gpt
Apparently, BIOS does not see a bootable device. In the dim past, fdisk
could set a partition as "active", which was i
Hi,
Dan Norton wrote:
> # fdisk -l
> ...
> Disklabel type: gpt
> In the dim past, fdisk
> could set a partition as "active", which was its euphemism for "bootable".
I guess, this applies only to MBR partition tables, not to GPT as on your
disk.
As Pascal stated, there is a bit defined in GPT to
Le 01/12/2017 à 19:57, Greg Wooledge a écrit :
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
Disklabel type: gpt
Apparently, BIOS does not see a bootable device. In the dim past, fdisk
could set a partition as "active", which was its euphemism for "bootable".
However now:
GPT
On Fri, Dec 01, 2017 at 01:57:37PM -0500, Greg Wooledge wrote:
> On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
> > Disklabel type: gpt
>
> > Apparently, BIOS does not see a bootable device. In the dim past, fdisk
> > could set a partition as "active", which was its euphemism for "boo
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
> Disklabel type: gpt
> Apparently, BIOS does not see a bootable device. In the dim past, fdisk
> could set a partition as "active", which was its euphemism for "bootable".
> However now:
GPT disk labels don't have active/bootable partit
>So my question: If I don't want to use the BIOS's Fake RAID, and want
>to
>use only the Linux kernel's software RAID, do I want to turn RAID off
>in
>the BIOS
Yes.
Also, always prefer dmraid over some fake RAID.
-nik
On 08/09/15 14:09, Darac Marjal wrote:
Just as a point of interest, I understand that most BIOS limits are
limits in the ATA command set (that is, PATA and SATA drives experience
these issues).
Looking at
http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/2tib-disc-limit.html
I see tha
On Mon, Sep 07, 2015 at 07:43:12PM -0400, shawn wilson wrote:
>
> On Sep 7, 2015 9:47 AM, "Ken Heard" <[1]kensli...@teksavvy.com> wrote:
> >
>
> >
> > Is there any limit to the size of a USB flash drive with the ext2 file
> > system encrypted on it which can be addressed through the BIOS
> > inte
On Sep 8, 2015 6:51 AM, "Pascal Hambourg" wrote:
>
> shawn wilson a écrit :
> >
> > (which uefi uses for boot).
>
> So what ? Who needs an EFI system partition bigger than the recommended
> 512 MB ?
>
Maybe he was trying to use a bigger partition? Do you have a better idea
what's happening?
Was
shawn wilson a écrit :
>
> IIRC, 32 GB is the limit of vfat
32 GiB is the maximum size of a FAT16 filesytem with 32-KiB clusters, or
of a FAT32 partition created by Windows XP and later. The limit of a
FAT32 filesystem is at least 2 TiB.
> (which uefi uses for boot).
So what ? Who needs an EFI
On Sep 7, 2015 9:47 AM, "Ken Heard" wrote:
>
>
> Is there any limit to the size of a USB flash drive with the ext2 file
> system encrypted on it which can be addressed through the BIOS
> interface? (I am using Debian Jessie.) The largest size I am now
> using is 32 gb drives but would like to us
On 05/03/14 22:08, Diogene Laerce wrote:
Hi,
Thanks for your answer.
Id like to install debian on a M10 from Meiying : does anybody know how
to access the BIOS ?
You need to gain root.
1. Download and intall:-
http://www.unlockroot.com/ (or a free program with similar funtionality)
2.
On 05/03/14 22:08, Diogene Laerce wrote:
> Hi,
>
> Thanks for your answer.
>
>>> Id like to install debian on a M10 from Meiying : does anybody know how
>>> to access the BIOS ?
>>>
>
>> You need to gain root.
>>
>> 1. Download and intall:-
>> http://www.unlockroot.com/ (or a free program with
Hi,
Thanks for your answer.
Id like to install debian on a M10 from Meiying : does anybody know how
to access the BIOS ?
Thank you
BIOS? They have a BIOS?
Actually I just assumed so.
You need to gain root.
1. Download and intall:-
http://www.unlockroot.com/ (or a free program with simi
On 28/02/14 23:35, Diogene Laerce wrote:
> Hi,
>
> Id like to install debian on a M10 from Meiying : does anybody know how
> to access the BIOS ?
>
> Thank you
>
BIOS? They have a BIOS?
You need to gain root.
1. Download and intall:-
http://www.unlockroot.com/ (or a free program with similar
On Thu, February 27, 2014 1:36 am, Weaver wrote:
> Hello all,
>
> I've got this old HP Compaq nx6120, that I want to change the boot
> sequence on as I've just installed tails on a USB drive and bought a new
> external DVD burner to provide what the internal standard player doesn't.
>
> I've forgo
On 27.2.2014 11:36, Weaver wrote:
I've forgotten what the original BIOS administrator password was, however,
so don't access to change the boot sequence.
http://h30499.www3.hp.com/t5/Notebook-HP-ProBook-EliteBook/Resetting-BIOS-password/td-p/695744
There someone suggests give it half hour with
On 27/02/14 20:46, Jonathan Dowland wrote:
> On 27/02/2014 09:36, Weaver wrote:
>> I've forgotten what the original BIOS administrator password was, however,
>> so don't access to change the boot sequence. If I remove the CMOS battery,
>> that should do it and I shouldn't lose anything other than t
On 27/02/2014 09:36, Weaver wrote:
> I've forgotten what the original BIOS administrator password was, however,
> so don't access to change the boot sequence. If I remove the CMOS battery,
> that should do it and I shouldn't lose anything other than the time?
Generally yes, that's the case.
--
It's like this:
> start here
>go down
> /\
> / \
> PROCESSOR i386 amd64
> | /|
> | / |
> |/ |
> HOST-KERNEL i386 amd64
> | /|
> | / |
>
Lina, let's tackle this one at a time.
First the VirtualBox problem.
What computer is this? Is it your Mac? As far as I know your Mac is 64
bit capable.
Virtual box comes in x86 and x86_64 versions. If you are running a
x86_64 distribution you can install the x86_64 version of VirtualBox and
a 6
>>
>> If in doubt, check the manual for your motherboard/computer. That will
>> tell you how to enter the BIOS menu.
>>
>
> It's still not so "readable" for me.
>
> It's HP Ethernet Boot Agent V9.4.5
>
It seems that I am not allowed to enter the BIOS menu? correct?
Thanks,
>
--
To UNSUBS
Furthermore, the root of this problem is that,
today I felt my laptop acting a bit retard, and something not as usual
happened. Like:
1] the ifconfig shows the IP, but still failed to connect the web. At
that time I just reboot and it worked.
2] Today, another thing acting not as before, it's ac
The origin problem is that when I used the virtualbox. it showed me
... This kernel requires an x86-64 CPU, but only detected an i686 CPU.
Unable to boot – please use a kernel appropriate for your CPU ...
Later google lead me to this page:
http://hereirestinremorse.wordpress.com/virtualbox/this-
1 - 100 of 144 matches
Mail list logo
