BookWormPUP64 problems with disk mount locations sdx...[solved]

[LANdpLAN]

When BWPUP64 10.09.9 boots to sdb1 everything works.
It won't boot to sdc or sdd
To make it boot to sdb1 i have to disconnect all other drives so that it's only the drive in the computer on sda and the puppy usb on sdb

I'm also saving my photos to an external hard drive and I have directed Shotwell to keep files in sdc1 which is where it was mounted the first time. Sometimes when I plug the drive in it mounts to sdd1 and i have to reconfigure shotwell.

Also, when puppy is booted to sdb and I plug in my drive, puppy gets remounted to sdc1 and my USBShotwell drive goes to sdd.

Is there a way to make puppy work no matter where it is mounted and a way to point shotwell to the name of the drive instead of it's mount point?

Edit#1 using udev https://oldforum.puppylinux.com/viewtopic.php?t=112558 I was able to give Shotwell the correct address for the photo library.
Trying to backup to another usb drive with grsyng I used udev to mount both. The grsync crashed when I clicked to 'open' the file browser to choose the source. Also the web browser didn't open. On restart I got these messages

[Geek3579]

I use the UUID of the drive where the frugal Puppy OS is located. You can get this from the Partition--> Information menu in GParted.
For simplicity, I assign this to a variable in the Grub2 grub.conf file -
eg: MYUUID=1c48a2d8-bdbb-4cf5-a620-e43c95e51a05

Then I use the value of this variable in the Grub boot code, for example, with a frugal Jammypup64 OS :
menuentry " Jammypup64" {
insmod ext2
search --no-floppy --fs-uuid --set $MYUUID
linux /Jammypup64/vmlinuz intel_pstate=disable net.ifnames=0 pmedia=usbflash pdrv=$MYUUID psubdir=/Jammypup64 pfix=fsck,fsckp TZ=AEST-10 nousbwait=5
initrd /Jammypup64/initrd.gz
}

There are other how-to-boot-puppyOS sites on the forum which provide more detail.

[bigpup]

Give us some information.

BookwormPup64 10.0.9 is installed on a USB stick?

How did you install it?
Give specific full details????

Are you ever accessing the computers bios boot device screen to select what device to boot from?

you need to do that if multiple different boot-able drives are plugged in.

It won't boot to sdc or sdd

What are these drives?
Are these drives that have a boot loader on them and some operating system to boot?

Are you booting to a working desktop of BookwormPup64.
Plugging in different drives or are they already plugged in when you boot?

[Trapster]

Maybe this will help:

https://oldforum.puppylinux.com/viewtopic.php?t=112558

[LANdpLAN]

I think I did frugal install BWPUP64 on a USB with uefi boot

sda is the internal disk with linux Mint legacy boot

The first boot I had to change the boot priority from legacy to uefi to get BWPUP. As long as I boot with the BWPUP usb plugged in, and nothing else, it always boots BWPUP. If I boot without BWPUP if boots Mint and then to reboot BWPUP I have to change the bios again.

When I talked about "won't boot to sdc or sdd" I meant that if I have other drives plugged in and they get accessed first at boot then they will be sdb and BWPUP will be sdc or sdd in which case it will not boot or if it does boot, some programs (I think the ones in the save file) will not run. It says i/o error. For example when I try to run shotwell.

Give us some information.

BookwormPup64 10.0.9 is installed on a USB stick?

How did you install it?
Give specific full details????

Are you ever accessing the computers bios boot device screen to select what device to boot from?

you need to do that if multiple different boot-able drives are plugged in.

It won't boot to sdc or sdd

What are these drives?
Are these drives that have a boot loader on them and some operating system to boot?

Are you booting to a working desktop of BookwormPup64.
Plugging in different drives or are they already plugged in when you boot?

[LANdpLAN]

I'm struggling to understand this. I'll have to think about it.

Maybe this will help:

https://oldforum.puppylinux.com/viewtopic.php?t=112558

[LANdpLAN]

16gig usb with BWPUP uuid=960B-D2AF

Where is the grub.conf file?

menuentry " BWpup64" {
insmod ext2
search --no-floppy --fs-uuid --set $960B-D2AF
linux /BWpup64/vmlinuz intel_pstate=disable net.ifnames=0 pmedia=usbflash pdrv=$960B-D2AF psubdir=/BWpup64 pfix=fsck,fsckp TZ=AEST-10 nousbwait=5
initrd /BWpup64/initrd.gz
}

Above is my attempt at putting in the correct substitutions from your code below. Do I delete/replace something in grub.conf with this or do I paste this into grub.com?

I use the UUID of the drive where the frugal Puppy OS is located. You can get this from the Partition--> Information menu in GParted.
For simplicity, I assign this to a variable in the Grub2 grub.conf file -
eg: MYUUID=1c48a2d8-bdbb-4cf5-a620-e43c95e51a05

Then I use the value of this variable in the Grub boot code, for example, with a frugal Jammypup64 OS :
menuentry " Jammypup64" {
insmod ext2
search --no-floppy --fs-uuid --set $MYUUID
linux /Jammypup64/vmlinuz intel_pstate=disable net.ifnames=0 pmedia=usbflash pdrv=$MYUUID psubdir=/Jammypup64 pfix=fsck,fsckp TZ=AEST-10 nousbwait=5
initrd /Jammypup64/initrd.gz
}

There are other how-to-boot-puppyOS sites on the forum which provide more detail.

[d-pupp]

@LANdpLAN Bookworm has a boot code that should help with your problem
psave=uuid
To find the uuid open a terminal and type

Code: Select all

lsblk -f

You can copy from the terminal by highlighting it with the mouse and paste it into you grub config by clicking the center mouse button (usually the wheel)

I am assuming you are using grub2 to boot so just add psave=uuid to your grub config at the end of the linux line. (Don't forget to add the comma ,psave=your-uuid )

DO NOT change you grub config other then that or may not be able to boot at all.

The problem you are having is because linux renames drive depending what else is plugged in first.
The uuid of a drive doesn't change even if the drive letter does.
BTW Bookworm may also have another boot code that you may have to use pupsfs=uuid

[Trapster]

Get rid of the $ signs in your grub.conf.

[bigpup]

The first boot I had to change the boot priority from legacy to uefi to get BWPUP. As long as I boot with the BWPUP usb plugged in, and nothing else, it always boots BWPUP. If I boot without BWPUP if boots Mint and then to reboot BWPUP I have to change the bios again.

That is normal operation of selecting a boot device for the bios to use.

If going into bios settings ->Boot ->device boot order setting.
It is only going to show devices hooked up, at the time you access the bios settings.
The order setting is use this device first, if not there use this one, if it is not there use this one.

But if you unplug and plug in drives. This setting is going to be wrong for what is now plugged in.

So you have to go back into the bios setup and correct it.

The bios is only going to see what is connected to the computer at the time you boot it.
Next time you boot, if not all the same drives are plugged into the computer.
The bios boot device order is wrong and it goes into what to choose that is there.
It always will eventually boot what is on the internal drive.
Usually with USB drives selected to first boot. If drive is not there it will default to the internal drive.

Most computers have a key you can press just as it gets power. (F9, F10, F11, etc... (depends on computer manufacture which one)
This will open a boot device selection screen showing all the bootable devices it sees connected to the computer.
Go down this list and select the one to boot.

[bigpup]

first boot I had to change the boot priority from legacy to uefi to get BWPUP.

That is because you only have a UEFI boot loader on the BookwormPup64 USB.

I think I did frugal install BWPUP64 on a USB with uefi boot

[LANdpLAN]

@LANdpLAN Bookworm has a boot code that should help with your problem
psave=uuid
To find the uuid open a terminal and type

Code: Select all

lsblk -f

You can copy from the terminal by highlighting it with the mouse and paste it into you grub config by clicking the center mouse button (usually the wheel)

I am assuming you are using grub2 to boot so just add psave=uuid to your grub config at the end of the linux line. (Don't forget to add the comma ,psave=your-uuid )

DO NOT change you grub config other then that or may not be able to boot at all.

The problem you are having is because linux renames drive depending what else is plugged in first.
The uuid of a drive doesn't change even if the drive letter does.
BTW Bookworm may also have another boot code that you may have to use pupsfs=uuid

Thanks, I found the uuid d3fee9d3-f23c-456b-9ce6-1a3e26f9d1d5 for my BWPUP USB.

my grub file config-6.1.119 is 259594 characters so I can not post it all here. I searched the file for "psave" and nothing was found.

Can you be more specific about what I need to change/add and where?

[d-pupp]

Thanks, I found the uuid d3fee9d3-f23c-456b-9ce6-1a3e26f9d1d5 for my BWPUP USB.

my grub file config-6.1.119 is 259594 characters so I can not post it all here. I searched the file for "psave" and nothing was found.

Can you be more specific about what I need to change/add and where?

@LANdpLAN If you are using grub2 find the line that starts with Linux and add to it.

Code: Select all

 pupsfs=d3fee9d3-f23c-456b-9ce6-1a3e26f9d1d5 psave=d3fee9d3-f23c-456b-9ce6-1a3e26f9d1d5

This should allow grub to find your boot files even if the usb key has a different drive designation.

[LANdpLAN]

I wanted to make puppy on an ext4 and the only method that worked was using grub4DOS

[LANdpLAN]

I can't remember exactly how I made my usb. I think I used the Frugal pup installer e4StickPup

I don't know where is grub.conf
I found grub.cfg.
it says:

Code: Select all

#
set default=0
set timeout=5

set menu_color_normal='yellow/blue'
set menu_color_highlight='black/cyan'

if [ $grub_platform = 'efi' ]; then
  if [ -n "$shim_lock" ]; then
    loadfont (memdisk)/fonts/unicode.pf2
  else
    loadfont /boot/grub/fonts/DejaVuSansMono18.pf2
  fi
  set gfxmode=auto
  terminal_output gfxterm
fi

menuentry "Puppy dpupbw64 10.0.9" {
  insmod ext2
  set bootid=bd9ac4ab-168e-413d-ae78-0ccd3633f4b5
  search --no-floppy --fs-uuid --set=root ${bootid}
  echo "Loading vmlinuz"
  linux /pups/dpupbw64/vmlinuz net.ifnames=0 pmedia=usbhd pdrv=lin99448a7c psubdir=/pups/dpupbw64 pfix=fsck,fsckp TZ=PST8PDT,M3.2.0,M11.1.0
  if [ -e /pups/dpupbw64/local-initrd.gz ]; then
    set local_rd=/pups/dpupbw64/local-initrd.gz
  else
    set local_rd=
  fi
  if [ -e /pups/dpupbw64/ucode.cpio ]; then
    set ucode_rd=/pups/dpupbw64/ucode.cpio
    echo "Loading ucode.cpio and initrd.gz"
  else
    set ucode_rd=
    echo "Loading initrd.gz"
  fi
  initrd ${ucode_rd} /pups/dpupbw64/initrd.gz ${local_rd}
}
if [ $grub_platform = 'efi' ]; then
  menuentry "System BIOS setup" {
    fwsetup
  }
fi
menuentry "Shutdown computer" {
  halt
}
menuentry "Reboot computer" {
  reboot
}

The uuid for my external hard drive with shotwell is ca89e3f4-b0db-4b17-8714-2ece9eee672a

[esos]

I wanted to make puppy on an ext4 and the only method that worked was using grub4DOS

grub4DOS works only for legacy-bios computer.
grub2 works on both computers(efi and legacy bios).

I found grub.cfg.
The uuid for my external hard drive with shotwell is ca89e3f4-b0db-4b17-8714-2ece9eee672a

Just type blkid in your terminal.
It will show all partition-id(s) you have.

[LANdpLAN]

I use the UUID of the drive where the frugal Puppy OS is located. You can get this from the Partition--> Information menu in GParted.
For simplicity, I assign this to a variable in the Grub2 grub.conf file -
eg: MYUUID=1c48a2d8-bdbb-4cf5-a620-e43c95e51a05

Then I use the value of this variable in the Grub boot code, for example, with a frugal Jammypup64 OS :
menuentry " Jammypup64" {
insmod ext2
search --no-floppy --fs-uuid --set $MYUUID
linux /Jammypup64/vmlinuz intel_pstate=disable net.ifnames=0 pmedia=usbflash pdrv=$MYUUID psubdir=/Jammypup64 pfix=fsck,fsckp TZ=AEST-10 nousbwait=5
initrd /Jammypup64/initrd.gz
}

There are other how-to-boot-puppyOS sites on the forum which provide more detail.

where in the Grub2 grub.conf file located?

[LANdpLAN]

Some questions I can't post to this old forum.

Maybe this will help:

https://oldforum.puppylinux.com/viewtopic.php?t=112558

run "mkrule" from the console in
/root/udev: "./mkrule /dev/sdX DeviceName" (where 'X' is the USB drive you wish to use, and "DeviceName"
is the friendly name you give the disk)

My attempt:

Code: Select all

# ./mkrule /dev/sdd Shotwell
bash: ./mkrule: No such file or directory
# 

[bigpup]

When BWPUP64 10.09.9 boots to sdb1 everything works.
It won't boot to sdc or sdd
To make it boot to sdb1 i have to disconnect all other drives so that it's only the drive in the computer on sda and the puppy usb on sdb

I'm also saving my photos to an external hard drive and I have directed Shotwell to keep files in sdc1 which is where it was mounted the first time. Sometimes when I plug the drive in it mounts to sdd1 and i have to reconfigure shotwell.

Also, when puppy is booted to sdb and I plug in my drive, puppy gets remounted to sdc1 and my USBShotwell drive goes to sdd.

Is there a way to make puppy work no matter where it is mounted and a way to point shotwell to the name of the drive instead of it's mount point?

I am going back to your first post and try to give you some useful help.

But to do it you have to provide good information on what exactly you are doing. Details, Details, Details????

So here goes!

I am going to assume you can get the Puppy USB stick install to boot to a working desktop, and it seems to be running OK.

To make it boot to sdb1 I have to disconnect all other drives so that it's only the drive in the computer on sda and the puppy usb on sdb

Drive identifications are given based on what drives are found connected to computer.
With one internal drive and a Puppy on a USB stick, no other drives.
The internal drive is sda
The Puppy USB stick is sdb.
Then it breaks down by partitions on the drive.
If a single partition is on each drive it would be sda1 and sdb1.
More partitions on the drive would be identified as 2, 3, 4, etc.....

If there are more drives connected to the computer.
How they are identified is determined by how the computers bios sees them.
The computers bios will usually look for internal connected drives first then find external connected ones, but the order it finds them can affect what they are identified as.
With several other internal or external drives connected.
The Puppy USB stick could be found as the 3rd, 4th, or 5th, etc... drive the bios finds connected.
So it could be identified as sdc1, sdd1, sde1, etc...............

when using Puppy to run the computer.
If you can keep all external drives connected to the same connection points.

The drive identifiers should stay to being the same between boots.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Do you know about boot device order setting in the computers bios?

This setting is the order the bios uses the drives to boot the computer. (the drive does have to have a boot loader on it to be seen as a boot device)

What the drive is called in the listing of boot devices could be anything based on what the bios sees it as.
You have to look at what is listed for devices and figure out what the internal drive is, the Puppy USB stick is, etc.........

This boot device order setting is what device is tried to boot from first, 2nd, 3rd, 4th, etc.........
If the Puppy USB stick is listed first, then it will try to boot from it first.
If not there try the 2nd in the list etc.............
If you can keep the Puppy USB stick connected in the same connection this device order setting should only need set one time to correct order to use.

If you unplug the Puppy USB stick and reconnect it to a different connection point.
Next time you boot, the bios may see it as a device in a different location and throws off the device order you had setup.
To boot from it you would need to correct the bios boot device order setting.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------

Also, when puppy is booted to sdb and I plug in my drive, puppy gets remounted to sdc1 and my USBShotwell drive goes to sdd.

This is when the computer is running from the Puppy USB stick and Puppy is in control of the computer?
You are not unplugging the Puppy USB stick while it is controlling the computer?

If yes.

This is not normal operation.

Maybe the computers connection controller is doing this. Maybe switching to a different controller.

Maybe have the Puppy USB stick plugged into a different USB connection point.
Boot the computer using this setup.

I need to know.

Is the Puppy save file/folder also located on the Puppy USB stick?

[esos]

@LANdpLAN
where in the Grub2 grub.conf file located?

If you installed Grub2, the file location is in /boot/grub/grub.cfg (by default) Not grub.conf.

[mikewalsh]

@LANdpLAN :-

Sounds to me as though what you need is "udev-rules". Jafadmin's wee mount-point utility worked brilliantly for me some years ago on the old Compaq Presario desktop rig, in the days before it eventually shuffled off its mortal coil.....

https://oldforum.puppylinux.com/viewtopic.php?t=112558

I was using a permanently plugged-in Seagate 'Expansion' USB 3.0 external hard drive at the time, and when experimenting with "suspend" discovered that Puppy WOULD insist on re-mounting the Seagate at the next mount-point up, i.e., sdb1 would become sdc1.....and then sdd1, sde1, sdf1, etc, through repeated suspend cycles. Which was no good at all if you were trying to script for stuff in a 'fixed' location!

(I don't have the issue with this HP Pavilion rig, as I ripped the guts out of the afore-mentioned external USB HDD, and it's now installed as a secondary internal 'data' drive via SATA cable direct to the mobo.)

=============================

This originally came as a collection of small files that needed to be manually put into the correct locations. I think jafadmin must have thrown the "ReadMe" file together in rather a hurry; it was a bit 'hacky', and didn't read all that smoothly.....so I edited the "ReadMe" file to make it more comprehensible, and assembled everything into a .pet package. One click, BANG! all installed, and ready to go.

I've attached the .pet below.

It places a text file called "README_Udev-Rules" in /root. Please read this BEFORE you do anything else, as it explains exactly what you need to do in order to create your "friendly", permanent mount-points(s). Apart from this, jafa's scripts still work as well as they ever did.

If you decide to give this a try, please let us know if it helps at all. I may have gotten hold of the wrong end of the stick here..!

Mike.

[dimkr]

A drive that disappears and re-appears can happen if voltage is too low and you have multiple USB devices connected at the same time. If this is the case, you should consider a powered USB hub.

[LANdpLAN]

Success! Thank you.

@LANdpLAN :-

Sounds to me as though what you need is "udev-rules". Jafadmin's wee mount-point utility worked brilliantly for me some years ago on the old Compaq Presario desktop rig, in the days before it eventually shuffled off its mortal coil.....

https://oldforum.puppylinux.com/viewtopic.php?t=112558

I was using a permanently plugged-in Seagate 'Expansion' USB 3.0 external hard drive at the time, and when experimenting with "suspend" discovered that Puppy WOULD insist on re-mounting the Seagate at the next mount-point up, i.e., sdb1 would become sdc1.....and then sdd1, sde1, sdf1, etc, through repeated suspend cycles. Which was no good at all if you were trying to script for stuff in a 'fixed' location!

(I don't have the issue with this HP Pavilion rig, as I ripped the guts out of the afore-mentioned external USB HDD, and it's now installed as a secondary internal 'data' drive via SATA cable direct to the mobo.)

=============================

This originally came as a collection of small files that needed to be manually put into the correct locations. I think jafadmin must have thrown the "ReadMe" file together in rather a hurry; it was a bit 'hacky', and didn't read all that smoothly.....so I edited the "ReadMe" file to make it more comprehensible, and assembled everything into a .pet package. One click, BANG! all installed, and ready to go.

I've attached the .pet below.

It places a text file called "README_Udev-Rules" in /root. Please read this BEFORE you do anything else, as it explains exactly what you need to do in order to create your "friendly", permanent mount-points(s). Apart from this, jafa's scripts still work as well as they ever did.

If you decide to give this a try, please let us know if it helps at all. I may have gotten hold of the wrong end of the stick here..!

Mike.

[LANdpLAN]

A drive that disappears and re-appears can happen if voltage is too low and you have multiple USB devices connected at the same time. If this is the case, you should consider a powered USB hub.

How to I test if voltage is the problem?

[dimkr]

How to I test if voltage is the problem?

Try to run dmesg and check if you see frequent errors about devices that don't respond, each followed by connection of the same device.

[LANdpLAN]

How to I test if voltage is the problem?

Try to run dmesg and check if you see frequent errors about devices that don't respond, each followed by connection of the same device.

What am i looking for?

Code: Select all

[    0.015265] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000dffff]
[    0.015266] PM: hibernation: Registered nosave memory: [mem 0x000e0000-0x000fffff]
[    0.015268] PM: hibernation: Registered nosave memory: [mem 0x20000000-0x201fffff]
[    0.015270] PM: hibernation: Registered nosave memory: [mem 0x40000000-0x401fffff]
[    0.015272] PM: hibernation: Registered nosave memory: [mem 0xbaa1e000-0xbaa61fff]
[    0.015274] PM: hibernation: Registered nosave memory: [mem 0xbadb7000-0xbade6fff]
[    0.015275] PM: hibernation: Registered nosave memory: [mem 0xbade7000-0xbafe6fff]
[    0.015276] PM: hibernation: Registered nosave memory: [mem 0xbafe7000-0xbaffefff]
[    0.015278] PM: hibernation: Registered nosave memory: [mem 0xbb000000-0xbb7fffff]
[    0.015278] PM: hibernation: Registered nosave memory: [mem 0xbb800000-0xbf9fffff]
[    0.015279] PM: hibernation: Registered nosave memory: [mem 0xbfa00000-0xfed1bfff]
[    0.015280] PM: hibernation: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
[    0.015281] PM: hibernation: Registered nosave memory: [mem 0xfed20000-0xffbfffff]
[    0.015282] PM: hibernation: Registered nosave memory: [mem 0xffc00000-0xffc1ffff]
[    0.015283] PM: hibernation: Registered nosave memory: [mem 0xffc20000-0xffffffff]
[    0.015285] [mem 0xbfa00000-0xfed1bfff] available for PCI devices
[    0.015286] Booting paravirtualized kernel on bare hardware
[    0.015289] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[    0.023284] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:16 nr_cpu_ids:16 nr_node_ids:1
[    0.023856] percpu: Embedded 61 pages/cpu s212992 r8192 d28672 u262144
[    0.023869] pcpu-alloc: s212992 r8192 d28672 u262144 alloc=1*2097152
[    0.023872] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15 
[    0.023917] Fallback order for Node 0: 0 
[    0.023921] Built 1 zonelists, mobility grouping on.  Total pages: 2034254
[    0.023922] Policy zone: Normal
[    0.023924] Kernel command line: BOOT_IMAGE=/pups/dpupbw64/vmlinuz net.ifnames=0 pmedia=usbflash pdrv=lin99448a7c psubdir=/pups/dpupbw64 pfix=fsck,fsckp TZ=PST8PDT,M3.2.0,M11.1.0
[    0.024064] Unknown kernel command line parameters "BOOT_IMAGE=/pups/dpupbw64/vmlinuz pmedia=usbflash pdrv=lin99448a7c psubdir=/pups/dpupbw64 pfix=fsck,fsckp TZ=PST8PDT,M3.2.0,M11.1.0", will be passed to user space.
[    0.024563] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[    0.024808] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    0.025033] mem auto-init: stack:all(zero), heap alloc:on, heap free:off
[    0.025043] software IO TLB: area num 16.
[    0.050636] Memory: 3043768K/8266768K available (18445K kernel code, 3182K rwdata, 12260K rodata, 3016K init, 16792K bss, 291992K reserved, 0K cma-reserved)
[    0.051022] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
[    0.051042] Kernel/User page tables isolation: enabled
[    0.051091] ftrace: allocating 53268 entries in 209 pages
[    0.061376] ftrace: allocated 209 pages with 4 groups
[    0.062563] Dynamic Preempt: voluntary
[    0.062633] rcu: Preemptible hierarchical RCU implementation.
[    0.062634] rcu: 	RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=16.
[    0.062636] 	Trampoline variant of Tasks RCU enabled.
[    0.062637] 	Rude variant of Tasks RCU enabled.
[    0.062637] 	Tracing variant of Tasks RCU enabled.
[    0.062638] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.062639] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=16
[    0.069468] NR_IRQS: 524544, nr_irqs: 552, preallocated irqs: 16
[    0.069672] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.071309] Console: colour VGA+ 80x25
[    0.071330] printk: console [tty0] enabled
[    0.071366] ACPI: Core revision 20220331
[    0.071480] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
[    0.071496] APIC: Switch to symmetric I/O mode setup
[    0.071498] DMAR: Host address width 36
[    0.071500] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.071506] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap c0000020e60262 ecap f0101a
[    0.071509] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    0.071517] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap c9008020660262 ecap f0105a
[    0.071519] DMAR: RMRR base: 0x000000badc6000 end: 0x000000badd5fff
[    0.071520] DMAR: RMRR base: 0x000000bb800000 end: 0x000000bf9fffff
[    0.071523] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    0.071525] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.071526] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[    0.072107] DMAR-IR: Enabled IRQ remapping in x2apic mode
[    0.072111] x2apic enabled
[    0.072119] Switched APIC routing to cluster x2apic.
[    0.072580] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.091496] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x23f50e36caf, max_idle_ns: 440795203453 ns
[    0.091505] Calibrating delay loop (skipped), value calculated using timer frequency.. 4989.06 BogoMIPS (lpj=9978136)
[    0.091533] CPU0: Thermal monitoring enabled (TM1)
[    0.091554] process: using mwait in idle threads
[    0.091557] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
[    0.091559] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
[    0.091563] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.091565] Spectre V2 : Mitigation: Retpolines
[    0.091566] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.091567] Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT
[    0.091568] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.091570] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.091571] Spectre V2 : User space: Mitigation: STIBP via prctl
[    0.091573] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
[    0.091575] MDS: Mitigation: Clear CPU buffers
[    0.091576] MMIO Stale Data: Unknown: No mitigations
[    0.091581] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.091583] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.091584] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.091585] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.091587] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[    0.111771] Freeing SMP alternatives memory: 48K
[    0.111777] pid_max: default: 32768 minimum: 301
[    0.111871] LSM: Security Framework initializing
[    0.111896] landlock: Up and running.
[    0.111897] Yama: disabled by default; enable with sysctl kernel.yama.*
[    0.111941] AppArmor: AppArmor initialized
[    0.111943] TOMOYO Linux initialized
[    0.111949] LSM support for eBPF active
[    0.112017] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.112031] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.113340] smpboot: CPU0: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz (family: 0x6, model: 0x2a, stepping: 0x7)
[    0.113507] cblist_init_generic: Setting adjustable number of callback queues.
[    0.113509] cblist_init_generic: Setting shift to 4 and lim to 1.
[    0.113536] cblist_init_generic: Setting adjustable number of callback queues.
[    0.113537] cblist_init_generic: Setting shift to 4 and lim to 1.
[    0.113557] cblist_init_generic: Setting adjustable number of callback queues.
[    0.113558] cblist_init_generic: Setting shift to 4 and lim to 1.
[    0.113576] Performance Events: PEBS fmt1+, SandyBridge events, 16-deep LBR, full-width counters, Intel PMU driver.
[    0.113597] ... version:                3
[    0.113598] ... bit width:              48
[    0.113599] ... generic registers:      4
[    0.113600] ... value mask:             0000ffffffffffff
[    0.113601] ... max period:             00007fffffffffff
[    0.113602] ... fixed-purpose events:   3
[    0.113603] ... event mask:             000000070000000f
[    0.113775] signal: max sigframe size: 1776
[    0.113796] Estimated ratio of average max frequency by base frequency (times 1024): 1228
[    0.113827] rcu: Hierarchical SRCU implementation.
[    0.113829] rcu: 	Max phase no-delay instances is 1000.
[    0.114989] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
----deleted because messages can't be so long...

[    2.658685] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[    2.658959] i8042: Warning: Keylock active
[    2.660401] serio: i8042 KBD port at 0x60,0x64 irq 1
[    2.660408] serio: i8042 AUX port at 0x60,0x64 irq 12
[    2.660553] mousedev: PS/2 mouse device common for all mice
[    2.660588] rtc_cmos 00:02: RTC can wake from S4
[    2.660883] rtc_cmos 00:02: registered as rtc0
[    2.660919] rtc_cmos 00:02: setting system clock to 2025-04-09T06:08:14 UTC (1744178894)
[    2.660952] rtc_cmos 00:02: alarms up to one year, y3k, 242 bytes nvram
[    2.661150] intel_pstate: Intel P-state driver initializing
[    2.661238] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[    2.661382] sdhci: Secure Digital Host Controller Interface driver
[    2.661384] sdhci: Copyright(c) Pierre Ossman
[    2.661400] sdhci-pci 0000:0b:00.0: SDHCI controller found [1217:8221] (rev 5)
[    2.661621] mmc0 bounce up to 128 segments into one, max segment size 65536 bytes
[    2.661755] mmc0: SDHCI controller on PCI [0000:0b:00.0] using DMA
[    2.661858] wbsd: Winbond W83L51xD SD/MMC card interface driver
[    2.661860] wbsd: Copyright(c) Pierre Ossman
[    2.661884] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.661914] ledtrig-cpu: registered to indicate activity on CPUs
[    2.662290] hid: raw HID events driver (C) Jiri Kosina
[    2.662330] usbcore: registered new interface driver usbhid
[    2.662331] usbhid: USB HID core driver
[    2.687603] NET: Registered PF_INET6 protocol family
[    2.689551] Segment Routing with IPv6
[    2.689577] In-situ OAM (IOAM) with IPv6
[    2.689598] mip6: Mobile IPv6
[    2.689602] NET: Registered PF_PACKET protocol family
[    2.689637] mpls_gso: MPLS GSO support
[    2.690086] microcode: sig=0x206a7, pf=0x10, revision=0x2f
[    2.690105] microcode: Microcode Update Driver: v2.2.
[    2.690112] IPI shorthand broadcast: enabled
[    2.690138] sched_clock: Marking stable (2688136716, 1795239)->(2696456256, -6524301)
[    2.690509] registered taskstats version 1
[    2.690520] Loading compiled-in X.509 certificates
[    2.691692] zswap: loaded using pool lzo/zbud
[    2.691948] Key type .fscrypt registered
[    2.691950] Key type fscrypt-provisioning registered
[    2.692657] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity=yes
[    2.693258] Key type encrypted registered
[    2.693263] AppArmor: AppArmor sha1 policy hashing enabled
[    2.693271] ima: No TPM chip found, activating TPM-bypass!
[    2.693273] ima: Allocated hash algorithm: sha256
[    2.693285] ima: No architecture policies found
[    2.693302] evm: Initialising EVM extended attributes:
[    2.693303] evm: security.selinux
[    2.693304] evm: security.SMACK64 (disabled)
[    2.693305] evm: security.SMACK64EXEC (disabled)
[    2.693306] evm: security.SMACK64TRANSMUTE (disabled)
[    2.693306] evm: security.SMACK64MMAP (disabled)
[    2.693307] evm: security.apparmor
[    2.693308] evm: security.ima
[    2.693309] evm: security.capability
[    2.693309] evm: HMAC attrs: 0x1
[    2.820226] clk: Disabling unused clocks
[    2.822550] Freeing unused decrypted memory: 2036K
[    2.823158] Freeing unused kernel image (initmem) memory: 3016K
[    2.823246] Write protecting the kernel read-only data: 32768k
[    2.823963] Freeing unused kernel image (text/rodata gap) memory: 2032K
[    2.824056] Freeing unused kernel image (rodata/data gap) memory: 28K
[    2.885994] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    2.885997] x86/mm: Checking user space page tables
[    2.893815] usb 1-1: new high-speed USB device number 2 using ehci-pci
[    2.913813] usb 2-1: new high-speed USB device number 2 using ehci-pci
[    2.930193] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    2.930204] Run /init as init process
[    2.930205]   with arguments:
[    2.930206]     /init
[    2.930207]   with environment:
[    2.930208]     HOME=/
[    2.930209]     TERM=linux
[    2.930209]     BOOT_IMAGE=/pups/dpupbw64/vmlinuz
[    2.930210]     pmedia=usbflash
[    2.930211]     pdrv=lin99448a7c
[    2.930212]     psubdir=/pups/dpupbw64
[    2.930212]     pfix=fsck,fsckp
[    2.930213]     TZ=PST8PDT,M3.2.0,M11.1.0
[    3.050619] usb 1-1: New USB device found, idVendor=8087, idProduct=0024, bcdDevice= 0.00
[    3.050641] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.051000] hub 1-1:1.0: USB hub found
[    3.051253] hub 1-1:1.0: 6 ports detected
[    3.070710] usb 2-1: New USB device found, idVendor=8087, idProduct=0024, bcdDevice= 0.00
[    3.070725] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.071408] hub 2-1:1.0: USB hub found
[    3.071689] hub 2-1:1.0: 8 ports detected
[    3.337916] usb 1-1.5: new high-speed USB device number 3 using ehci-pci
[    3.357922] usb 2-1.2: new high-speed USB device number 3 using ehci-pci
[    3.538322] usb 2-1.2: New USB device found, idVendor=18a5, idProduct=0302, bcdDevice= 1.10
[    3.538336] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.538339] usb 2-1.2: Product: STORE N GO
[    3.538340] usb 2-1.2: Manufacturer: Verbatim
[    3.538342] usb 2-1.2: SerialNumber: 071835B3A084D119
[    3.538847] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[    3.539162] scsi host6: usb-storage 2-1.2:1.0
[    3.612729] usb 1-1.5: New USB device found, idVendor=1bcf, idProduct=2802, bcdDevice=1c.09
[    3.612749] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.612755] usb 1-1.5: Product: Laptop_Integrated_Webcam_FHD
[    3.612760] usb 1-1.5: Manufacturer: CN0CJ3P27248726MA32NA02
[    3.617915] usb 2-1.3: new low-speed USB device number 4 using ehci-pci
[    3.732067] usb 2-1.3: New USB device found, idVendor=045e, idProduct=0752, bcdDevice= 3.00
[    3.732087] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.732094] usb 2-1.3: Product: Wired Keyboard 400
[    3.732099] usb 2-1.3: Manufacturer: Microsoft
[    3.736547] input: Microsoft Wired Keyboard 400 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:045E:0752.0001/input/input2
[    3.870278] hid-generic 0003:045E:0752.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Wired Keyboard 400] on usb-0000:00:1d.0-1.3/input0
[    3.949935] usb 2-1.4: new low-speed USB device number 5 using ehci-pci
[    3.984153] block device autoloading is deprecated and will be removed.
[    3.984583] block device autoloading is deprecated and will be removed.
[    3.984997] block device autoloading is deprecated and will be removed.
[    3.985321] block device autoloading is deprecated and will be removed.
[    3.985640] block device autoloading is deprecated and will be removed.
[    3.985980] block device autoloading is deprecated and will be removed.
[    3.986313] block device autoloading is deprecated and will be removed.
[    3.986629] block device autoloading is deprecated and will be removed.
[    4.063073] usb 2-1.4: New USB device found, idVendor=046d, idProduct=c018, bcdDevice=43.01
[    4.063091] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.063098] usb 2-1.4: Product: USB Optical Mouse
[    4.063103] usb 2-1.4: Manufacturer: Logitech
[    4.066795] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/0003:046D:C018.0002/input/input3
[    4.067294] hid-generic 0003:046D:C018.0002: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:1d.0-1.4/input0
[    4.149908] usb 2-1.8: new full-speed USB device number 6 using ehci-pci
[    4.285248] usb 2-1.8: New USB device found, idVendor=0a5c, idProduct=5800, bcdDevice= 1.01
[    4.285268] usb 2-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.285274] usb 2-1.8: Product: 5880
[    4.285279] usb 2-1.8: Manufacturer: Broadcom Corp
[    4.285283] usb 2-1.8: SerialNumber: 0123456789ABCD
[    4.285758] usb 2-1.8: config 0 descriptor??
[    4.557307] scsi 6:0:0:0: Direct-Access     Verbatim STORE N GO       PMAP PQ: 0 ANSI: 6
[    4.683544] sd 6:0:0:0: [sdb] 30322688 512-byte logical blocks: (15.5 GB/14.5 GiB)
[    4.685559] sd 6:0:0:0: [sdb] Write Protect is off
[    4.685574] sd 6:0:0:0: [sdb] Mode Sense: 45 00 00 00
[    4.687313] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    4.698375]  sdb: sdb1 sdb2
[    4.698759] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[    6.059339] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Quota mode: none.
[   16.025823] random: crng init done
[   23.452114] loop0: detected capacity change from 0 to 913856
[   23.456327] overlayfs: "xino" feature enabled using 2 upper inode bits.
[   34.215417] loop1: detected capacity change from 0 to 30920
[   34.219488] overlayfs: "xino" feature enabled using 3 upper inode bits.
[   34.222882] loop2: detected capacity change from 0 to 223864
[   34.226323] overlayfs: "xino" feature enabled using 3 upper inode bits.
[   34.229796] loop3: detected capacity change from 0 to 146704
[   34.233349] overlayfs: "xino" feature enabled using 4 upper inode bits.
[   34.236786] loop4: detected capacity change from 0 to 20952
[   34.240514] overlayfs: "xino" feature enabled using 4 upper inode bits.
[   34.244156] loop5: detected capacity change from 0 to 167536
[   34.247691] overlayfs: "xino" feature enabled using 4 upper inode bits.
[  137.937705] loop6: detected capacity change from 0 to 16777215
[  138.263916] EXT4-fs (loop6): mounted filesystem with ordered data mode. Quota mode: none.
[  138.334807] overlayfs: "xino" feature enabled using 4 upper inode bits.
[  138.700360] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[  139.122113] zsmalloc: module verification failed: signature and/or required key missing - tainting kernel
[  139.125022] zram: Added device: zram0
[  139.146313] zram0: detected capacity change from 0 to 15621128
[  139.162598] Adding 7810560k swap on /dev/zram0.  Priority:-2 extents:1 across:7810560k SSFS
[  140.065110] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input4
[  140.077877] ACPI: button: Lid Switch [LID]
[  140.077973] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5
[  140.078499] ACPI: button: Power Button [PBTN]
[  140.078573] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input6
[  140.078613] ACPI: button: Sleep Button [SBTN]
[  140.078667] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input7
[  140.079082] ACPI: button: Power Button [PWRF]
[  140.089175] ACPI: AC: AC Adapter [AC] (on-line)
[  140.205477] ACPI: battery: Slot [BAT0] (battery present)
[  140.207059] ACPI: battery: Slot [BAT1] (battery absent)
[  140.208969] ACPI: battery: Slot [BAT2] (battery absent)
[  140.314914] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
[  140.318520] i801_smbus 0000:00:1f.3: Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration
[  140.318527] i2c i2c-0: 2/2 memory slots populated (from DMI)
[  140.320046] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20220331/utaddress-204)
[  140.320056] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[  140.320060] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20220331/utaddress-204)
[  140.320066] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[  140.320068] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000053F (\_SB.PCI0.PEG0.VID.GPSP) (20220331/utaddress-204)
[  140.320073] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20220331/utaddress-204)
[  140.320077] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[  140.320079] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000053F (\_SB.PCI0.PEG0.VID.GPSP) (20220331/utaddress-204)
[  140.320083] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20220331/utaddress-204)
[  140.320087] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[  140.320088] lpc_ich: Resource conflict(s) found affecting gpio_ich
[  140.320519] i2c i2c-0: Successfully instantiated SPD at 0x50
[  140.336724] e1000e: Intel(R) PRO/1000 Network Driver
[  140.336729] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[  140.336998] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[  140.399917] input: PC Speaker as /devices/platform/pcspkr/input/input8
[  140.401201] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
[  140.437665] ACPI: bus type drm_connector registered
[  140.489604] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[  140.521713] parport_pc 00:04: [io  0x0378-0x037b]
[  140.523222] parport_pc 00:04: activated
[  140.523228] parport_pc 00:04: reported by Plug and Play ACPI
[  140.643053] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) d4:be:d9:49:9f:3f
[  140.643061] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[  140.643093] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: 3041FF-0FF
[  140.684675] snd_hda_intel 0000:01:00.1: Disabling MSI
[  140.684684] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[  140.692473] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  140.692597] sr 1:0:0:0: Attached scsi generic sg1 type 5
[  140.692713] sd 6:0:0:0: Attached scsi generic sg2 type 0
[  140.767037] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[  140.805269] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input10
[  140.805310] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input11
[  140.844872] mc: Linux media interface: v0.10
[  140.867796] cfg80211: Loaded X.509 cert 'benh@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf'
[  140.868116] cfg80211: Loaded X.509 cert 'romain.perier@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[  140.868431] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[  140.868755] cfg80211: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[  140.870228] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[  140.870389] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[  140.908852] videodev: Linux video capture interface: v2.00
[  141.066574] ACPI Warning: \_SB.PCI0.PEG0.VID._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20220331/nsarguments-61)
[  141.067424] pci 0000:01:00.0: optimus capabilities: enabled, status dynamic power, hda bios codec supported
[  141.067436] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG0.VID_ handle
[  141.067474] nouveau 0000:01:00.0: enabling device (0004 -> 0007)
[  141.067616] nouveau 0000:01:00.0: NVIDIA GF119 (0d9160a1)
[  141.184394] nouveau 0000:01:00.0: bios: version 75.19.6a.01.01
[  141.337477] nouveau 0000:01:00.0: fb: 512 MiB DDR3
[  141.361247] Intel(R) Wireless WiFi driver for Linux
[  141.361397] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[  141.371559] usb 1-1.5: Found UVC 1.00 device Laptop_Integrated_Webcam_FHD (1bcf:2802)
[  141.379840] iwlwifi 0000:03:00.0: firmware: direct-loading firmware iwlwifi-6000-4.ucode
[  141.380004] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532 6000-4.ucode op_mode iwldvm
[  141.386954] i915 0000:00:02.0: [drm] Disabling ppGTT for VT-d support
[  141.387162] i915 0000:00:02.0: [drm] VT-d active for gfx access
[  141.387300] i915 0000:00:02.0: vgaarb: deactivate vga console
[  141.387884] Console: switching to colour dummy device 80x25
[  141.388072] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[  141.388076] i915 0000:00:02.0: [drm] DMAR active, disabling use of stolen memory
[  141.398119] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[  141.413608] input: Laptop_Integrated_Webcam_FHD: I as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input12
[  141.413663] usbcore: registered new interface driver uvcvideo
[  141.425540] i915 0000:00:02.0: [drm] Skipping intel_backlight registration
[  141.425600] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 1
[  141.553116] nouveau 0000:01:00.0: DRM: VRAM: 512 MiB
[  141.553124] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[  141.553129] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[  141.553132] nouveau 0000:01:00.0: DRM: DCB version 4.0
[  141.553135] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000323 00010034
[  141.553139] nouveau 0000:01:00.0: DRM: DCB outp 01: 02011300 00000000
[  141.553142] nouveau 0000:01:00.0: DRM: DCB outp 02: 08024382 00020010
[  141.553145] nouveau 0000:01:00.0: DRM: DCB outp 03: 020323a6 0f220010
[  141.553147] nouveau 0000:01:00.0: DRM: DCB outp 04: 02032362 00020010
[  141.553149] nouveau 0000:01:00.0: DRM: DCB outp 05: 040433b6 0f220010
[  141.553151] nouveau 0000:01:00.0: DRM: DCB outp 06: 04043372 00020010
[  141.553154] nouveau 0000:01:00.0: DRM: DCB conn 00: 00000041
[  141.553156] nouveau 0000:01:00.0: DRM: DCB conn 01: 00000100
[  141.553159] nouveau 0000:01:00.0: DRM: DCB conn 02: 00001246
[  141.553161] nouveau 0000:01:00.0: DRM: DCB conn 03: 00002346
[  141.553163] nouveau 0000:01:00.0: DRM: DCB conn 04: 00010461
[  141.554771] nouveau 0000:01:00.0: DRM: MM: using COPY0 for buffer copies
[  141.573590] ACPI: video: Video Device [VID] (multi-head: yes  rom: yes  post: no)
[  141.578584] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[  141.578590] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[  141.578592] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[  141.578593] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
[  141.602564] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:00/input/input13
[  141.610528] ACPI: video: Video Device [VID1] (multi-head: yes  rom: no  post: no)
[  141.612336] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input14
[  141.615897] acpi device:15: registered as cooling_device4
[  141.619373] acpi device:41: registered as cooling_device5
[  141.619421] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[  141.619696] vga_switcheroo: enabled
[  141.652844] fbcon: i915drmfb (fb0) is primary device
[  141.657716] at24 0-0050: supply vcc not found, using dummy regulator
[  141.658245] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[  141.663289] at24 0-0050: 256 byte spd EEPROM, read-only
[  141.764853] iTCO_vendor_support: vendor-support=0
[  141.846723] nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
[  141.850168] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
[  141.871554] ppdev: user-space parallel port driver
[  141.985909] nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
[  142.129911] nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
[  142.443149] input: AlpsPS/2 ALPS DualPoint Stick as /devices/platform/i8042/serio1/input/input15
[  142.456559] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input9
[  142.552045] Console: switching to colour frame buffer device 170x48
[  142.570018] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[  142.606622] iTCO_wdt iTCO_wdt.1.auto: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
[  142.606914] iTCO_wdt iTCO_wdt.1.auto: initialized. heartbeat=30 sec (nowayout=0)
[  142.607973] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.4)
[  142.608990] dell-smbios A80593CE-A997-11DA-B012-B622A1EF5492: WMI SMBIOS userspace interface not supported(0), try upgrading to a newer BIOS
[  142.612557] input: Dell WMI hotkeys as /devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input16
[  142.644960] snd_hda_codec_idt hdaudioC0D0: autoconfig for 92HD90BXX: line_outs=1 (0xe/0x0/0x0/0x0/0x0) type:line
[  142.644969] snd_hda_codec_idt hdaudioC0D0:    speaker_outs=1 (0xd/0x0/0x0/0x0/0x0)
[  142.644973] snd_hda_codec_idt hdaudioC0D0:    hp_outs=1 (0xb/0x0/0x0/0x0/0x0)
[  142.644976] snd_hda_codec_idt hdaudioC0D0:    mono: mono_out=0x0
[  142.644979] snd_hda_codec_idt hdaudioC0D0:    inputs:
[  142.644981] snd_hda_codec_idt hdaudioC0D0:      Dock Mic=0xf
[  142.644984] snd_hda_codec_idt hdaudioC0D0:      Internal Mic=0x11
[  142.644987] snd_hda_codec_idt hdaudioC0D0:      Mic=0xa
[  142.684623] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
[  142.684701] input: HDA Intel PCH Dock Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
[  142.684774] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input19
[  142.684852] input: HDA Intel PCH Dock Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input20
[  142.684921] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input21
[  147.178400] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[  147.290083] Bluetooth: Core ver 2.22
[  147.290114] NET: Registered PF_BLUETOOTH protocol family
[  147.290115] Bluetooth: HCI device and connection manager initialized
[  147.290120] Bluetooth: HCI socket layer initialized
[  147.290122] Bluetooth: L2CAP socket layer initialized
[  147.290126] Bluetooth: SCO socket layer initialized
[  147.299995] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  147.300000] Bluetooth: BNEP filters: protocol multicast
[  147.300005] Bluetooth: BNEP socket layer initialized
[  147.550106] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[  147.797951] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[  148.267992] wlan0: authenticate with c8:d7:19:3a:97:ae
[  148.334713] wlan0: send auth to c8:d7:19:3a:97:ae (try 1/3)
[  148.360614] wlan0: authenticated
[  148.360916] wlan0: waiting for beacon from c8:d7:19:3a:97:ae
[  148.413851] wlan0: associate with c8:d7:19:3a:97:ae (try 1/3)
[  148.437908] wlan0: RX AssocResp from c8:d7:19:3a:97:ae (capab=0x411 status=0 aid=9)
[  148.452620] wlan0: associated
[  148.522218] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  149.064896] ACPI: \_SB_.PCI0.PEG0.VID_: failed to evaluate _DSM
[  150.782445] nouveau 0000:01:00.0: Enabling HDA controller
[  164.206432] ACPI: \_SB_.PCI0.PEG0.VID_: failed to evaluate _DSM
[  208.862285] nouveau 0000:01:00.0: Enabling HDA controller
[  215.338183] ACPI: \_SB_.PCI0.PEG0.VID_: failed to evaluate _DSM

[LANdpLAN]

@LANdpLAN Bookworm has a boot code that should help with your problem
psave=uuid
To find the uuid open a terminal and type

Code: Select all

lsblk -f

You can copy from the terminal by highlighting it with the mouse and paste it into you grub config by clicking the center mouse button (usually the wheel)

I am assuming you are using grub2 to boot so just add psave=uuid to your grub config at the end of the linux line. (Don't forget to add the comma ,psave=your-uuid )

DO NOT change you grub config other then that or may not be able to boot at all.

The problem you are having is because linux renames drive depending what else is plugged in first.
The uuid of a drive doesn't change even if the drive letter does.
BTW Bookworm may also have another boot code that you may have to use pupsfs=uuid

this is my grub.cfg

#
set default=0
set timeout=5

set menu_color_normal='yellow/blue'
set menu_color_highlight='black/cyan'

if [ $grub_platform = 'efi' ]; then
if [ -n "$shim_lock" ]; then
loadfont (memdisk)/fonts/unicode.pf2
else
loadfont /boot/grub/fonts/DejaVuSansMono18.pf2
fi
set gfxmode=auto
terminal_output gfxterm
fi

menuentry "Puppy dpupbw64 10.0.9" {
insmod ext2
set bootid=bd9ac4ab-168e-413d-ae78-0ccd3633f4b5
search --no-floppy --fs-uuid --set=root ${bootid}
echo "Loading vmlinuz"
linux /pups/dpupbw64/vmlinuz net.ifnames=0 pmedia=usbflash pdrv=lin99448a7c psubdir=/pups/dpupbw64 pfix=fsck,fsckp TZ=PST8PDT,M3.2.0,M11.1.0
if [ -e /pups/dpupbw64/local-initrd.gz ]; then
set local_rd=/pups/dpupbw64/local-initrd.gz
else
set local_rd=
fi
if [ -e /pups/dpupbw64/ucode.cpio ]; then
set ucode_rd=/pups/dpupbw64/ucode.cpio
echo "Loading ucode.cpio and initrd.gz"
else
set ucode_rd=
echo "Loading initrd.gz"
fi
initrd ${ucode_rd} /pups/dpupbw64/initrd.gz ${local_rd}
}
if [ $grub_platform = 'efi' ]; then
menuentry "System BIOS setup" {
fwsetup
}
fi
menuentry "Shutdown computer" {
halt
}
menuentry "Reboot computer" {
reboot
}

I'm still having troubles. Did I miss something? I see the correct uuid: bd9ac4ab-168e-413d-ae78-0ccd3633f4b5
where do i add psave=uuid?

[dimkr]

What am i looking for?

Errors, at the bottom, and you'll need to reproduce this problem first. Rebooting will clear this log.

[d-pupp]

@LANdpLAN

This is from the help file in Vanilladpup

• pmedia=usbflash: activates PUPMODE 13 (see PUPMODE).
• pupsfs=name|UUID|label: specifies the partition containing SFSs using its name, UUID or label, and disables search for this partition.
• psave=name|UUID|label: specifies the partition containing save folders or files using its name, UUID or label, and disables search for this partition.
• psubdir=/relative/path: specifies a subdirectory for SFSs and a save folders or files.

linux /pups/dpupbw64/vmlinuz net.ifnames=0 pmedia=usbflash pdrv=lin99448a7c psubdir=/pups/dpupbw64 pfix=fsck,fsckp TZ=PST8PDT,M3.2.0,M11.1.0

Make a backup copy before you start messing with so you can restore it if needed.

You can add psave to the linux line above. Space separated. I'm not sure if the order matters but I would insert it just before pfix=

Also pdrv=uuid in the linux line is not the same uuid you posted. You might need to change that as well
I'm trying to remember if pdrv was replaced in Bookworm with pupsfs. Can someone confirm please.?

Thanks d-pupp

[LANdpLAN]

Code: Select all

gdk-pixbuf-query-loaders --update-cache

this solved my issue of the operating system not being able to launch apps after I plug in my external usb drive.

Chat GPT said this about automating it so I have done so.

how can i do gdk-pixbuf-query-loaders --update-cache after everytime I plug in a usb drive?
ChatGPT said:

Great question — and very Puppy Linux of you! Since USB replugging can mess with the environment, here’s how to automatically run gdk-pixbuf-query-loaders --update-cache every time you plug in a USB drive.
Option 1: Add it to /etc/rc.d/rc.local

This will run it at every boot (covers most reboots or cold-plug scenarios):

Open a terminal and edit the file:

geany /etc/rc.d/rc.local

Add this just before the final exit 0:

gdk-pixbuf-query-loaders --update-cache

Save and reboot to test.

Pros: Simple, persistent.
Cons: Doesn’t handle hotplug (i.e. when you plug in the USB while the system is already running).
Option 2: Use a udev rule (for hotplug detection)

This is a bit more advanced but powerful — it runs a command whenever a USB is plugged in.

Create a rule:

geany /etc/udev/rules.d/99-usbloaderfix.rules

Paste this in:

ACTION=="add", SUBSYSTEM=="block", KERNEL=="sd[b-z][0-9]", RUN+="/usr/local/bin/fix-pixbuf"

This detects USB storage devices (/dev/sdb1, /dev/sdc1, etc.).

Create the script:

mkdir -p /usr/local/bin
geany /usr/local/bin/fix-pixbuf

Paste this in:

#!/bin/sh
gdk-pixbuf-query-loaders --update-cache

Make it executable:

chmod +x /usr/local/bin/fix-pixbuf

Reload udev rules:

udevadm control --reload-rules

Pros: Automatically runs the fix as soon as you plug in a drive.
Cons: Might not fire in all cases depending on Puppy’s limited udev setup.
Bonus: Combine both for reliability

If Puppy’s udev doesn't reliably trigger hotplug events, using both the rc.local method and the udev rule gives you the best chance of always having working GdkPixbuf loaders.

Want a script that pops up a notification too (like “Fix applied!”) when you plug in a drive?
You said:
there is no exit 0. it says: #this file called from rc.sysinit
#you can edit this file
#When firewall is installed, will append lines to this file...
ChatGPT said:

Ah, gotcha — you're seeing the stripped-down version of rc.local that Puppy Linux uses. Totally normal in Puppy — it's a lightweight system, and that file often doesn't have exit 0 like in standard Debian/Ubuntu.

No worries! You can still safely add your command to that file.
Here's What to Do:

Open the file:

geany /etc/rc.d/rc.local

Add this line at the bottom of the file (but outside any commented-out sections):

gdk-pixbuf-query-loaders --update-cache

Save and close.

There’s no need to add exit 0 in Puppy’s rc.local — it will still execute the lines during boot. Puppy hooks into it from rc.sysinit, so anything you add in there will run.
Optional: Log output (in case you want to debug later)

You can also modify it like this to log output:

gdk-pixbuf-query-loaders --update-cache >> /tmp/pixbuffix.log 2>&1