No CD drive. Now what?

Status
Not open for further replies.
so I guess I am still nowhere.

If os-prober fails to find the correct Linux partitions, then running update-grub will fail.

You could install GParted (partition editor) either from your software centre or with the command

Code:
sudo apt install gparted

and see if it reveals anything, other than that, it may be a complete reinstall or another computer.

Wizard
 


I guess the lesson her is that the hype for Linux Mint: "It just works" https://forums.linuxmint.com/viewtopic.php?t=314730 should be adjusted too Linux Mint: "It's just hype."
And I quote.
"It just works"

That statement is based on certain user's experiences.
Linux Mint is not the "The Holy Grail".

Any Linux distro can be problematic with some hardware.

To properly find a solution a user needs to post some system specs.

Type of computer make and model.
Processor and amount of memory etc.

Posting it's an old Windows XP computer just doesn't cut it.

Certain Linux distros with certain DE work better on some hardware than other Linux distros will.

More info you can give the more chance at a better solution.
 
Oh man I can't remember how many times I had to reinstall XP when it was current. I ran out of my auto-authenticate quota and had to call to talk to a human at least 2 dozen times. Definately not "It just works" .

Right about that time is when I found Knoppix and the joys of Linux live distros. Now I am 100% M$ free and run Porteux full time. It more than just works: it rocks.

Vektor
 
Oh man I can't remember how many times I had to reinstall XP when it was current. I ran out of my auto-authenticate quota and had to call to talk to a human at least 2 dozen times. Definately not "It just works" .

Vektor
I had very few problems with Windows XP and sad to see it reach EOL back in April of 2014.

I used Vista and didn't have any of the problems that I read about that others were having but my computers were built for Vista.

I started using Linux prior to Windows XP EOL
 
Code:
$ cat /etc/default/grub
# 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=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false

# 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_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"

So then I try os-prober as suggested.

Code:
sudo os-prober
/dev/sda1:Windows 7:Windows:chain
/dev/sda4:Windows Recovery Environment:Windows1:chain
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.

so I guess I am still nowhere.
That's a good start. os-prober is picking up Windows...

Now edit... sudo nano /etc/default/grub
Do everything @wizardfromoz suggested, plus uncomment this line:
#GRUB_DISABLE_OS_PROBER=false
so it reads:
GRUB_DISABLE_OS_PROBER=false
And save (Ctrl + o) and exit (Ctrl + x).
Okay, now just
sudo su
update-grub
*If errors occur, post them and the output of /boot/grub/device.map

Otherwise
Ctl + d / exit
And you should be good. Restart.

A little bit of advice: Backup & Nuke is sometimes better. Get the latest version of Mint (22.1) and just wipe everything and run Mint only... I'd strongly suggest looking into pure Debian or antiX Linux for that machine though. Mint + XFCE is still on the heavy side.antiX will work OOTB and you can install a more mid-weight DE if thebdefault, Rox, isn't good enough.
 
James, on

, plus uncomment this line:
#GRUB_DISABLE_OS_PROBER=false
so it reads:
GRUB_DISABLE_OS_PROBER=false

...not necessary, if the Member is using a version of Linux Mint from 21.0 onwards (currently up to 22.1 'Xia')

When update-grub is run, it begins by sourcing the following

Code:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/50_linuxmint.cfg'
Generating grub configuration file ..

That file /etc/default/grub.d/50_linuxmint.cfg contains as in the Spoiler below (for new members, click the Spolier to open and click again if you wish to close it)

Code:
chris@Xia-Xfce-WD:~$ cat /etc/default/grub.d/50_linuxmint.cfg
#! /bin/sh
set -e

# Set distributor to "Ubuntu"
#
# In Mint 16:
# shim and grub come with hardcoded ubuntu strings upstream, without this EFI installation is broken
# https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1242417
#
# In Mint 17:
# Despite the bug report being marked as fixed, the situation is the same. Grub was patched by Ubuntu
# to assign the "ubuntu" distributor ID when it was given "Kubuntu". That results in Kubuntu finally
# getting EFI to work out of the box but still using "ubuntu" as far as grub-install is concerned.
# So we'll stick to "Ubuntu" for this iteration.
#
# In Mint 18:
# Some packages are still hardcoded with the "ubuntu" path.. fwupdate for instance.
# Visually, the grub boot menuentry name is set for derivatives in 10_linux,
# but underneath the EFI path remains "ubuntu" for everything to work properly.

GRUB_DISTRIBUTOR="Ubuntu"

# Re-enable OS Prober
# Since Mint 21
# https://lists.gnu.org/archive/html/grub-devel/2021-03/msg00120.html
GRUB_DISABLE_OS_PROBER=false

Note the bottom 4 lines in particular.

If that file has content in it that differs to that in /etc/default/grub (and it does), then it will take priority, so update-grub will launch the script /etc/grub.d/30_os-prober , which in turn executes os-prober.

Cheers

Wizard
 
Oh man I can't remember how many times I had to reinstall XP when it was current. I ran out of my auto-authenticate quota and had to call to talk to a human at least 2 dozen times. Definately not "It just works" .

Right about that time is when I found Knoppix and the joys of Linux live distros. Now I am 100% M$ free and run Porteux full time. It more than just works: it rocks.

personal experience on my own hardware:
- from 98se to win7, I was flattening/reloading probably every 8 to 10 months on average. 8.1 was a bit more stable and win10 was the most stable os I've ever experienced, but I dropped that back in December to hang out with you fine folks.

personal experience in a corporate setting:
- in the winxp/win7 days I'd reimage at least 3 machines a week. some weeks were a lot worse than others. these days, with win11, I'm down to an average of about 1 per week - some weeks I dont reimage at all and I'll tell you, it feels weird.

I'll toss Porteux in a vm and take a look at it, never heard of that distro until just now.
 
Hello to theLegionWithin

If Porteux proves to be interesting then register and introduce yourself on the forum. It is a nice place just like here, though not as broad a scope of topics.


Hope to see ya there

Vektor
 
"OFF-TOPIC".....and no real help (but I'll mention it anyway)

I could suggest 'Puppy' Linux.....but I won't.

'Our Pup' is odd even by Linux standards, and I still - and always will - maintain that beginners/noobs NEED to gain experience in the mainstream before venturing through the doors of 'Puppyland'....especially given that she's a "hobbyist" distro, intended for those that enjoy pulling their system to pieces and re-building it to suit themselves.

IMHO, 'Puppy' would probably work wonders with that hardware, but I doubt the OP will ever get the chance to find out. Some folks are technically-minded.....and some simply aren't.

Fact of life, I'm afraid.....sorry an' all that.

(shrug.....)


Mike. o_O
 
Last edited:
Hey Mike

I also have Puppy SL15 tweaked really nice, so don't be so quick to dismiss. Thanks to you and others I think Puppy is a good place to start.

Vektor
 
Is this thread hijacked yet?

Still hangin' , totalnoob ?
 
@Vektor :-

Hey Mike

I also have Puppy SL15 tweaked really nice, so don't be so quick to dismiss. Thanks to you and others I think Puppy is a good place to start.

Vektor
Nah, I'm not being "quick to dismiss", mate. The Duck is right when he says Puppy is 'unique'!

Since Puppy does so many things differently to the mainstream distros, I don't think it's really fair for noobs to 'learn' with Puppy.....because when they invariably want to try out other distros, they then have to learn the nuts'n'bolts all over again. And that never made much sense to me.

I'll help anyone with Puppy if they're genuinely interested. But to MY way of thinking, it's far better for them to get a handle on how the mainstream does things first.....because if they then don't like the way Puppy does things, or can't get their heads around it, they can simply return to the mainstream. And they should still know what they're doing.

No harm, no foul. I know it seems like I'm being a traitor to the cause, or even "elitist".....but that's not the case. At the end of the day, I'm thinking about the users, because when it boils down to it, without a user-base no distro would have much point in existing at all. Puppy really IS "different".

That's just me.


Mike. ;)
 
Last edited:
I use Puppy Linux for the most as it comes straight OOTB and it works and does what I need to do. Mission Accomplished.

If you really want to learn the ways of Puppy Linux you have to be willing to rifle through the Puppy Linux forums and ask questions.
 
I guess the lesson her is that the hype for Linux Mint: "It just works" https://forums.linuxmint.com/viewtopic.php?t=314730 should be adjusted too Linux Mint: "It's just hype."

I suspect that many millions of Mint users worldwide would disagree with you, but if your bad experience so far is legitimate and not just a trolling exercise, then a re-installation attempt by you might help you make a better judgement for or against.

Cheers

Wizard
 
James, on



...not necessary, if the Member is using a version of Linux Mint from 21.0 onwards (currently up to 22.1 'Xia')

When update-grub is run, it begins by sourcing the following

Code:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/50_linuxmint.cfg'
Generating grub configuration file ..

That file /etc/default/grub.d/50_linuxmint.cfg contains as in the Spoiler below (for new members, click the Spolier to open and click again if you wish to close it)

Code:
chris@Xia-Xfce-WD:~$ cat /etc/default/grub.d/50_linuxmint.cfg
#! /bin/sh
set -e

# Set distributor to "Ubuntu"
#
# In Mint 16:
# shim and grub come with hardcoded ubuntu strings upstream, without this EFI installation is broken
# https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1242417
#
# In Mint 17:
# Despite the bug report being marked as fixed, the situation is the same. Grub was patched by Ubuntu
# to assign the "ubuntu" distributor ID when it was given "Kubuntu". That results in Kubuntu finally
# getting EFI to work out of the box but still using "ubuntu" as far as grub-install is concerned.
# So we'll stick to "Ubuntu" for this iteration.
#
# In Mint 18:
# Some packages are still hardcoded with the "ubuntu" path.. fwupdate for instance.
# Visually, the grub boot menuentry name is set for derivatives in 10_linux,
# but underneath the EFI path remains "ubuntu" for everything to work properly.

GRUB_DISTRIBUTOR="Ubuntu"

# Re-enable OS Prober
# Since Mint 21
# https://lists.gnu.org/archive/html/grub-devel/2021-03/msg00120.html
GRUB_DISABLE_OS_PROBER=false

Note the bottom 4 lines in particular.

If that file has content in it that differs to that in /etc/default/grub (and it does), then it will take priority, so update-grub will launch the script /etc/grub.d/30_os-prober , which in turn executes os-prober.

Cheers

Wizard
Ah, that nice to know, I haven't really dug into my Mint VM since upgrading it (actually never dug much into it in that arena). I'm glad they enable default, I never understood why it started being disabled.
 
I never understood why it started being disabled.

There was an apprehension at the time by a number of Devs that it posed a security threat, and some reacted accordingly, but later that threat response was downscaled.

Off Topic somewhat, but it does not look like the OP is coming back, perhaps he was trolling.

Wiz
 
Off Topic somewhat, but it does not look like the OP is coming back, perhaps he was trolling.

Wouldn't be the first time. Not sure why people come here to complain about Linux. Reminds me of that Ricky Gervais sketch about guitar lessons:

MOD EDIT: Video contains adult language.

 
Last edited by a moderator:
If os-prober fails to find the correct Linux partitions, then running update-grub will fail.

You could install GParted (partition editor) either from your software centre or with the command

Code:
sudo apt install gparted

and see if it reveals anything, other than that, it may be a complete reinstall or another computer.

Wizard
I have done so (after returning from vaca) and I found nothing within the long trail of information that accompanies installations about grub. Then I ran the program itself from the main menu and there was nothing about grub. What was I looking for to tell me how to get grub installed and functioning? Recall that prior efforts found grub was not present.

So I moved on to another distro, called Manjaro, which is currently installing from a USB (I continued to be able to boot from USB under the weird, not specified BIOS option to do so). On install, I was not presented with an offer to save Mint though I was able to save Windows. I will advise if this turns out to be useful.

Do everything @wizardfromoz suggested, plus uncomment this line:
#GRUB_DISABLE_OS_PROBER=false *************
A little bit of advice: Backup & Nuke is sometimes better. Get the latest version of Mint (22.1) and just wipe everything and run Mint only... I'd strongly suggest looking into pure Debian or antiX Linux for that machine though. Mint + XFCE is still on the heavy side.antiX will work OOTB and you can install a more mid-weight DE if thebdefault, Rox, isn't good enough.

I don't know what a lot of that jargon means. I suppose with enough extra extra effort ...

Still hangin' , totalnoob ?

Yup.
ou mentioned having an install of Linux Mint 17, and then trying to upgrade to 18, and then 19. It doesn't say when you tried this but if you tried this recently it's not really of use because 17, 18 and 19 are all end of life so the repos are offline.

That would have been on Christmas Day 2019, a perfect time for using the Internet because no one else is. I remember having plans to visit family that day -- which is why I am ticked I had to babysit the computer -- and not having plans to visit anyone on Christmas or any other time until 2022. Yeah, that happened.
 
So I moved on to another distro, called Manjaro, which is currently installing from a USB (I continued to be able to boot from USB under the weird, not specified BIOS option to do so). On install, I was not presented with an offer to save Mint though I was able to save Windows. I will advise if this turns out to be useful.

I did it and, IMHO as par for the course with Linux, there was no failure to disappoint along the minimal amount of good.

The difficulty is that when I clicked the "install" tab, I was confronted with an error message stating I was not on line and that installation was not possible without it. Not too bad as I had a wifi dongle in place. I was reasonably quickly able to use the network controls to find my network, get it going and proceed to full install. This wiped out Mint, as I was given no option to use any partition other than the existing Mint partition for the permanent Manjaro installation.

I went away from the install for a few minutes not wanting to babysit it, and lo and behold, it installed well and asked for a reboot, which I performed. When it came back, I found Grub waiting for me, allowing me to choose between Manjaro and Windows -- the exact thing that Linux Mint could not do for me.

Alas, that was where the good news ended. The fully installed version of Manjaro not only did not recognize my dongle as its temporarily installed version had, it did not seem to have software to recognize wifi under any set of circumstances. No network control menu option showed me the available wifi networks; indeed no menu option was available to allow me to find or fiddle with a wifi adapter much less to connect to a network. I booted and rebooted; I pulled and replace the dongle; no recognition either way. I may try again with a different wifi dongle, but until then, I have no internet on the Linux OS other than to connect with a relay device that I share with my son that receives wifi but delivers it to a computer via ethernet wiring. (He uses it for his gaming console so my time with it is limited at best.)

So for all the effort, I am in the exact same situation I was on Christmas Day 2019 when I tried to upgrade from Linux Mint 2017 to 2019, an attempt that ended in total failure after many days' trials and tribulations and left me with no backup for Windows for about 5 years. But Manjaro is a lesser product than Linux Mint 2017 despite 8 years having passed, so I am in some ways worse off than before, though I should be able to recover my data if Windows goes down for the count.

A final cautionary tale: Manjaro also cannot play videos that Windows 7 from about 2010 can on that computer. I tried loading a video file and it played for about 3 or 4 seconds before my computer schizzed out with diagonal lines, effectively BSOD. I had to perform a hot reboot and I presumably would have lost work if something else was going when the machine crashed.

Ultimately Linux seems to suffice if you don't make a lot of demands on it and don't expect too much and if you don't mind a steep learning curve to attain a barely acceptable emergency solution for something like data retrieval in a crisis, especially if you are the guy who uses a computer as a mere tool for something other than being in the computing industry.
 
Last edited:
Status
Not open for further replies.


Members online


Top