|
You probably deleted the partition but didn't update your grub configs. As far as how to update Grub... I bet Google knows.
Jeremy Falcon
|
|
|
|
|
Hi,
I am running Slackware current with a 5.18.7 kernel. The motherboard it was running on has been switched, and because I was presented with a grub-rescue prompt (only after the motherboard switch, worked perfect prior to this) I chose to reinstall. Now what is happening is the grub-rescue prompt it displayed on the screen for a second or 2 and then the normal grub menu shows up and boots properly. I can't figure out how to fix this for the main drive was formatted and partitioned during install. It has 2 partitions on it a 4GB swap and the remainder of the 2TB drive for /. The second drive is also a 2TB drive both same make and model and has 1 partition on it /home which was not formatted during install, so all the files and so forth remain intact after the user is re-added. I should mention I am using grub version 2.06. Any help on this would be greatly appreciated.
|
|
|
|
|
Example:
$ ./0-current_working_directory
/root/alx-system_engineering-devops/0x00-shell_basics
$
Repo:
GitHub repository: alx-system_engineering-devops
Directory: 0x00-shell_basics
File: 0-current_working_directory
|
|
|
|
|
You seem to have forgotten to ask a question.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I am looking for someone who is very familiar with the subject.
Running Ubuntu 21.xx and I am unable to activate this feature ever since I switched to 21.xx.
My initial grub menu contains several OS , I managed to option " no flash " and get nice "progress report " during boot. I just cannot option "run last active OS" - no asterisk (*) in base grub menu..
When I do "update grub" the OS identified DO NOT match the main boot menu.
Please do not waste your time with "RTFM" or "it runs fine for me".
Ask for clarification instead if you do not get it.
Any real help would be greatly appreciated.
PS. This is boot problem, hence NO "cut / copy/ screen shot / paste " is not available - do not ask for photo.
|
|
|
|
|
|
I have checked the grub file many times - here is my current copy .
and this is my "save last used ' option
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
I have been checking the validity of my grub using this option
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
it works as expected.
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
#GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
|
|
|
|
|
According to my reading of the documentation that should work, so I am afraid I have no more ideas.
|
|
|
|
|
You may or may not have access to a GRUB environment block (of which you make no mention).
Quote: For safety reasons, this storage is only available when installed on a plain disk (no LVM or RAID), using a non-checksumming filesystem (no ZFS), and using BIOS or EFI functions (no ATA, USB or IEEE1275).
grub-mkconfig uses this facility to implement ‘GRUB_SAVEDEFAULT’ (see Simple configuration).
GNU GRUB Manual 2.06
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
I have a copy of "dmesg" , presumably "boot process " log.
Is there a way to identify actual "grub" file used ?
I am still puzzled why I am receiving the boot messages AFTER I
uncommented "splash" option.
|
|
|
|
|
Quote: The environment block is a preallocated 1024-byte file, which normally lives in /boot/grub/grubenv (although you should not assume this). At boot time, the load_env command (see load_env) loads environment variables from it, and the save_env (see save_env) command saves environment variables to it. From a running system, the grub-editenv utility can be used to edit the environment block.
GNU GRUB Manual 2.06: Environment block
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
SOLVED?
The UEFI setup has an option "F11" - boot menu, it brings up grub menu. This menu, I call it "short version ", differs from what I have been using . And it matches output of "update-grub". After using it once I now have the " run last OS used" working. After boot I get this "short version" - with an asterisk indication of last OS used.
I did suspect UEFI from the start...which grub is actually used, optioned ???
BUT I have never updated UEFI and I am NOT going to risk more problems - so I'll leave it alone.
PS With "last OS used" working I no longer have "splash " disabled , no boot progress , - go figure...
|
|
|
|
|
For those who do not know - I am not welcomed to ask questions in Ubuntu forum...
( asked too many questions )
Using Ubuntu 21.10 and having this annoying problem
In "file manager" when asking for file "properties" I get two responses
1. Immediate display of current usage of hardware - that is what i wanted
2. File manager takes off and starts "scanning" all files, takes long time and really does not
provide simple information about how much (%) is in use on specific hardware...
Where is the resolution to this?
Is there an "properties" option I am missing ?
|
|
|
|
|
I just tried this and it works correctly. Whatever is happening on your system is unique to you, and may have something to do with previous questions which suggest that your installation is not very stable.
|
|
|
|
|
Isn't this something you can see from the source code?
That's the the great advantage of open source projects: If the system doesn't behave the way you want it to, you have the full freedom to go into the source code and modify it the way you want.
|
|
|
|
|
As a "user" why should I (have) to do that ?
It used to work just fine - giving a hardware usage in % ...
Now it ..... as posted.
Thanks for reply.
|
|
|
|
|
Member 14968771 wrote: As a "user" why should I (have) to do that ? Because it is Free and Open Source Software.
It is given to you so that you can fix it yourself. That is what the free-ness and open-ness is about. You may of course ask your friends to fix it for you, or even pay someone to fix it (although that sort of kills the "free" idea, at least in the sense of "free beer").
When you accept a "free" offer that is financed by ads and commercials, then you are the product being sold.
When you accept "free" and open sources software, then you are the maintainer of that software.
This is 101 FOSS.
|
|
|
|
|
How do you react to this :
run OS update - manually or automatically and after reboot get
'... OS is experienced internal error... (send us this message ) "
If you say " what do you expect for free " this discussions is over.
|
|
|
|
|
I am not allowed to post on Linux site, so I am posting here.
I have never done this so I am confused with these instructions.
I like to install the Qwt library "under" my Qt folder.
I am using QtCreator so my qmake is current and working, so I skipped verifying qmake.
qwt-6.2.0 folder did not exist on my system so I did
cd Qt
mkdir qwt-6.2.0
then I get lost what to do next...
this folder obviously does not exists in /Qt folder
/usr/local/Qt-5.0.1/bin/qmake qwt.pro
Unix-like systems
The first step before creating the Makefile is to check that the correct version of qmake is used. F.e. on older Linux distribution you often find a Qt3 qmake and in the path.
The default setting of qmake is to generate a makefile that builds Qwt for the same environment where the version of qmake has been built for. So creating a makefile usually means something like:
cd qwt-6.2.0
/usr/local/Qt-5.0.1/bin/qmake qwt.pro
The generated Makefile includes all paths related to the chosen Qt version and the next step is:
make
( On multicore systems you can speed up building the Qwt libraries with running several jobs simultaneously: f.e. "make -j4" on a dual core. )
Finally you have to install everything below the directories you have specified in qwtconfig.pri. Usually this is one of the system directories ( /usr/local, /opt, ... ) where you don't have write permission and then the installation needs to be done as root:
sudo make install
( On systems where sudo is not supported you can do the same with: su -c "make install" )
|
|
|
|
|
hci_tool "commands " are derived from "blueZ" library.
Using hci_tool commands in C/C++ (source )code is ....
The hci_tool scan command is implemented in "blueZ" as hci_inquire....
hci_tool --help give a nice overview of all the command options.
Is there a real (written) resource to "translate" hci_tool commands to "blueZ" library functions ?
OK - I found hci_lib.h where all the (function) declarations are...
Now if I can get FUNCTION DESCRIPTIONS I will be closer to "best guess" how hcitool commands and bluez function relate. Is there such documentation anywhere ?
It is NOT in "blueZ" on github .
?
modified 25-Mar-22 0:38am.
|
|
|
|
|
|
Thanks - that is what I am using. It is odd there is no documentation.
Most functions use same or similar variables , but...
for example "device_desc" and "dd" are same...
This "open" concept is not that open - somehow "job security" comes to mind instead...
Perhaps "Most commonly used variable names dictionary (u-tube) " is overdue.
int i = index of something...
int error = error number ( duh )
Have a great day
|
|
|
|
|
Member 14968771 wrote: for example "device_desc" and "dd" are same... Maybe, but that is not a rule that you can rely on.
|
|
|
|
|
It is against my conviction to use "blueZ' but ....
I am trying locate the actual library to link my program with.
From experience I know the file names change so I really do not know what to search for
bluez ... bluetooth..libbluetooth... libbluetooth.so...
I decided to remove and install and hoped for answers..
No go!
What name am I looking for and where is such file located?
Cheers
q5@q5-desktop $ sudo apt-get remove libbluetooth-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
libfwupdplugin1
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
libbluetooth-dev
0 upgraded, 0 newly installed, 1 to remove and 4 not upgraded.
After this operation, 847 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 195509 files and directories currently installed.)
Removing libbluetooth-dev:amd64 (5.60-0ubuntu2.2) ...
q5@q5-desktop $ sudo apt-get install libbluetooth-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
libfwupdplugin1
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
libbluetooth-dev
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 0 B/252 kB of archives.
After this operation, 847 kB of additional disk space will be used.
Selecting previously unselected package libbluetooth-dev:amd64.
(Reading database ... 195466 files and directories currently installed.)
Preparing to unpack .../libbluetooth-dev_5.60-0ubuntu2.2_amd64.deb ...
Unpacking libbluetooth-dev:amd64 (5.60-0ubuntu2.2) ...
Setting up libbluetooth-dev:amd64 (5.60-0ubuntu2.2) ...
q5@q5-desktop $
|
|
|
|
|
Short answer is you don't need to know. When linking your program with -lbluetooth should be enough, if it's installed in the usual place. Depending on what your development environment is, you can use pkg-config to tell you what flags you need to use to find headers and libs e.g
k5054@localhost:~$ pkg-config --cflags bluez
k5054@localhost:~$ pkg-config --libs bluez
-lbluetooth
k5054@localhost:~$ This tells us that we don't need any additional flags for compilation, and only need to add -lbluetooth when linking.
If you really want to know where the lib is, you can use dpkg to tell you where it is
k5054@localhost:~$ dpkg -S libbluetooth | grep .so
libbluetooth3:amd64: /usr/lib/x86_64-linux-gnu/libbluetooth.so.3
libbluetooth3:amd64: /usr/lib/x86_64-linux-gnu/libbluetooth.so.3.19.3
libbluetooth-dev:amd64: /usr/lib/x86_64-linux-gnu/libbluetooth.so
k5054@localhost:~$ Note that debian/ubuntu uses the target architecture as part of the filename for libraries, so for a PI with a 32 bit Raspberry Pi OS, the path is /usr/lib/arm-linux-gnueabihf/libbluetooth.so.3 , and it would be different again for a PI with a 64-bit OS, or an i386, MIPS, etc.
Keep Calm and Carry On
|
|
|
|