On Thu, Jun 20, 2024 at 3:57 PM Jeffrey Walton wrote:
>
> On Thu, Jun 20, 2024 at 9:23 AM Bhasker C V wrote:
> >
> > I generated a pr/pk pair and the kernel is signed. Placed them in the
> > kernel tree and compiled the kernel.
>
> I don't think you are supposed to check-in/compile-in the private
On Thu, Jun 20, 2024 at 9:23 AM Bhasker C V wrote:
>
> I generated a pr/pk pair and the kernel is signed. Placed them in the
> kernel tree and compiled the kernel.
I don't think you are supposed to check-in/compile-in the private key.
It is usually supposed to stay private.
> Could someone tell
Hi,
I generated a pr/pk pair and the kernel is signed. Placed them in the
kernel tree and compiled the kernel.
Could someone tell me what am I doing wrong please ?
Below is the status (I am using loader.efi from linuxfoundation)
When i boot debian stock kernel signed, i see that the secure boot
On Sun, Aug 27, 2023 at 22:51 David Wright wrote:
> On Sun 27 Aug 2023 at 14:27:09 (-0500), Tom Browder wrote:
> > On Sun, Aug 27, 2023 at 13:27 Greg Wooledge wrote:
> >
> > > On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> > > > When I boot the system, then the drives are not mounted as
On Sun 27 Aug 2023 at 14:27:09 (-0500), Tom Browder wrote:
> On Sun, Aug 27, 2023 at 13:27 Greg Wooledge wrote:
>
> > On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> > > When I boot the system, then the drives are not mounted as set in
> > /etc/fstab.
> > > For example, the SDD should mou
On Sun, Aug 27, 2023 at 13:27 Greg Wooledge wrote:
> On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> > When I boot the system, then the drives are not mounted as set in
> /etc/fstab.
> > For example, the SDD should mounted to /space, and the unencrypted HDD
...
> Use UUIDs or Labels ins
I am answering myself. It must be the opened UUID. Looks like this problem is
solved.
Thank you all for the fast response! I hope, my question was not too annoying.
But I am very very happy, to get this little issue so easily solved - and
learned something, too.
Thank you all, you made a man
So, now I added all UUIDs. But I am not quite sure for the enrcypted /home
partition. The UUID changes when the device is luks-opened.
Which one must be in the fstab? The one from "lsblk -f /dev/sda4" or
"lsblk -f /dev/mapper/home"?
Am Sonntag, 27. August 2023, 20:26:46 CEST schrieb Greg W
Here it is:
# /etc/fstab: static file system information.
#
#
proc/proc procdefaults0 0
# /dev/sda3 / ext4defaults,errors=remount-ro 0 1
UUID=819bf8ae-a727-4b5e-97f8-007f58e98f74 /
On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> Dear list,
>
> there is a little issue, which I try to solve. On my desptop computer I have
> 4
> harddrives:
>
> SATA 0: HDD 300 GB with Debian + GRUB on MBR (parted in /boot, /, /home
> (luks), /var (luks) and /usr (luks)
> SATA 1: HDD
Hans composed on 2023-08-27 20:19 (UTC+0200):
> When I boot the system, then the drives are not mounted as set in /etc/fstab.
> For example, the SDD should mounted to /space, and the unencrypted HDD shall
> be mounted to /daten.
> But it seems, sometimes the mountpoints are not correct, so the
On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> Dear list,
>
> there is a little issue, which I try to solve. On my desptop computer I have
> 4
> harddrives:
>
> SATA 0: HDD 300 GB with Debian + GRUB on MBR (parted in /boot, /, /home
> (luks), /var (luks) and /usr (luks)
> SATA 1: HDD
On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> When I boot the system, then the drives are not mounted as set in /etc/fstab.
> For example, the SDD should mounted to /space, and the unencrypted HDD shall
> be mounted to /daten.
>
> But it seems, sometimes the mountpoints are not correct
> When I boot the system, then the drives are not mounted as set in /etc/fstab.
I suspect that showing us your `/etc/fstab` would help,
Stefan
Dear list,
there is a little issue, which I try to solve. On my desptop computer I have 4
harddrives:
SATA 0: HDD 300 GB with Debian + GRUB on MBR (parted in /boot, /, /home
(luks), /var (luks) and /usr (luks)
SATA 1: HDD 300 GB with Win10
SATA 2: SDD 128 GB (as simple data storage)
SATA 3: HD
On Sat, 23 Nov 2019 22:25:01 -0800
Kord wrote:
> Hi,
>
> I recently installed Debian 10.2 as a dual boot on a second HDD separate
> from windows 10, and when booting from grub, have not been able to get
> pass the “ [ ok ] gnome display manager”. Is there any fix for this?
> Thanks
Without m
On 11/24/19, Kord wrote:
> I recently installed Debian 10.2 as a dual boot on a second HDD separate
> from windows 10, and when booting from grub, have not been able to get pass
> the “ [ ok ] gnome display manager”. Is there any fix for this?
You could try Ctrl+Alt+F1 (or F2) to test if you hav
On 16/03/14 07:12 PM, KS wrote:
> On 16/03/14 04:26 PM, Joe wrote:
>>
>> It appears to be an issue with the new grub-pc-bin 2.02~beta2-7. I
>> downgraded to 2.00-22 along with grub-common, and it booted again. I
>> then downgraded two other 2.02 packages marked as broken, and all was
>> well again.
On 16/03/14 04:26 PM, Joe wrote:
>
> It appears to be an issue with the new grub-pc-bin 2.02~beta2-7. I
> downgraded to 2.00-22 along with grub-common, and it booted again. I
> then downgraded two other 2.02 packages marked as broken, and all was
> well again.
>
Pinned packages and reinstalled 2
On Sun, 16 Mar 2014 14:40:21 -0400
X wrote:
> Hi,
>
> On Wed, I upgraded my debian box (unstable) using aptitude and then
> shut it down. On booting, it gave me an alert about a disk it
> couldn't find and brought up the Busybox prompt. I have /boot as a
> normal partition and other partitions (
On 16/03/14 02:40 PM, X wrote:
> Hi,
>
> On Wed, I upgraded my debian box (unstable) using aptitude and then shut
> it down. On booting, it gave me an alert about a disk it couldn't find
> and brought up the Busybox prompt. I have /boot as a normal partition
> and other partitions (/, /home, /tmp,
Hi,
On Wed, I upgraded my debian box (unstable) using aptitude and then shut
it down. On booting, it gave me an alert about a disk it couldn't find
and brought up the Busybox prompt. I have /boot as a normal partition
and other partitions (/, /home, /tmp, /usr, /var, etc.) in a LVM group.
On che
On Mon, Dec 20, 2010 at 10:51 AM, John W Foster wrote:
> On Sun, 2010-12-19 at 14:36 -0500, Tom H wrote:
>> On Sun, Dec 19, 2010 at 12:26 PM, John Foster wrote:
>>>
>>> Here's a new one for you GRUB2 gurus. I left my office attended by my 2 (5 &
>>> 7 yr. old very curious) grandsons. When about 3
On Sun, 2010-12-19 at 14:36 -0500, Tom H wrote:
> On Sun, Dec 19, 2010 at 12:26 PM, John Foster wrote:
> >
> > Here's a new one for you GRUB2 gurus. I left my office attended by my 2 (5 &
> > 7 yr. old very curious) grandsons. When about 3 minutes later I returned, my
> > system ( which is a mult
On Sun, Dec 19, 2010 at 12:26 PM, John Foster wrote:
>
> Here's a new one for you GRUB2 gurus. I left my office attended by my 2 (5 &
> 7 yr. old very curious) grandsons. When about 3 minutes later I returned, my
> system ( which is a multiple boot of Debian Linux SID, Windows 7 Pro, &
> Ubuntu 9,
Here's a new one for you GRUB2 gurus. I left my office attended by my 2
(5 & 7 yr. old very curious) grandsons. When about 3 minutes later I
returned, my system ( which is a multiple boot of Debian Linux SID,
Windows 7 Pro, & Ubuntu 9,) had been rebooted form Windows7 to the GRUB2
rescue mode &
Hi Franklin,
On Fri, July 3, 2009 4:36 pm, Frank Lin PIAT wrote:
> Your problem is probably inside your /boot/initrd... file
>
> You might want to "rebuild" it, using update-initramfs
Tried that, multiple ways:
update-initramfs -u -k all
update-initramfs -n -k all
> Also, did you read /usr/shar
Hi,
On Fri, 2009-07-03 at 12:53 +1000, Andrew McGlashan wrote:
>
> I have 2x IBM xSeries 346 servers, one has a RAID card (let's call this
> machine "346a") and the other only has onboard SCSI (346b).
>
> [..] it stops at a
> special initramfs sh after giving up on the lvm volume group (not fo
Hi,
I have 2x IBM xSeries 346 servers, one has a RAID card (let's call this
machine "346a") and the other only has onboard SCSI (346b).
Both have two RAID1 software mirrors -- one for /boot (/dev/md0) and the
other for lvm2 use (/dev/md1).
Both are running the same amd64 Debian release (Len
On Fri, Jan 14, 2000 at 02:01:43PM -0900, Christopher S. Swingley wrote:
> >
> > Any idea ?
>
> I had the same problem with an Adaptex 2910C. I think your problem is
> a kernel issue -- the 2.0.36 kernel that is loaded from the Debian CD
> doesn't support the newer Adaptec cards. This is why
> I try to install slink (debian 2.1), booting from the cd-rom 1, and I
> have no
> problem until:
> (scsi0) found at PCI 17/0
> (scsi0) Warning - detected auto-termination
> (scsi0) Downloading sequencer code... 419 instructions downloaded
>
> - After the 'Download sequencer code...' messag
Hello,
I try to install slink (debian 2.1), booting from the cd-rom 1, and I
have no
problem until the system tries to detect the scsi devices.
My PC is an Pentium 200MHz (non MMX) with 128MB
I have a SCSI controller which is an AHA-2940A
a PLEXTOR Model: CD-ROM PX-40TSRev: 1.00 (SCS
32 matches
Mail list logo
