Re: new install: configuring ethernet strangeness

[Felix Miata]

John Covici composed on 2022-06-18 04:21 (UTC-0400):

> Hi.  I just installed Debian Bullseye on a refurbished computer which
> I am going to use as a voip server.  Now, due to my ignorance, at the
> very end of the install, I selected to use #12 which said standard
> system items.

> Well, to my horror, I got gnome with all its dependencies.  I ran
> apt-get and purged all the gnome items.  However, my outgoing
> connection instead of being in /etc/network/interfaces is now managed
> by network-manager.  I don't want to use the gui, but there seems to
> be no good way to configure the connection, should I need to do so.
> /etc/systemd/network is  empty.

I think nmcli handles anything the GUI could, but I never have NetworkMangler
installed to test it.

> So, how can I either get back to /etc/network/interfaces or somehow
> manage the existing connection which is buried in
> /etc/NetworkManager/system-connections/  and is readable, but I could
> never change it.

Configure the interface in (e.g., for eth0) /etc/systemd/network/eth0.network.
Disable "managed" resolver; populate /etc/resolv.conf.
# systemctl enable systemd-networkd.service
# systemctl disable systemd-networkd-wait-online.service

The above is the short version of how I've been converting all my static
networking installations, which is all of them, minus the laptops. In addition,
your old networking config/system needs to be fully disabled and/or purged.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: new install: configuring ethernet strangeness

[John Covici]

Thanks everyone, this is what I think I will do, just use
network/interfaces.

On Sat, 18 Jun 2022 08:00:27 -0400,
Anssi Saari wrote:
> 
> John Covici  writes:
> 
> > So, how can I either get back to /etc/network/interfaces
> 
> This should be simple enough. Uninstall NetworkManager, package
> network-manager, edit /etc/network/interfaces as you like. The
> networking.service is used to run ifup and ifdown to configure and
> reconfigure the network with what's in /etc/network/interfaces.
> 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: new install: configuring ethernet strangeness

[Anssi Saari]

John Covici  writes:

> So, how can I either get back to /etc/network/interfaces

This should be simple enough. Uninstall NetworkManager, package
network-manager, edit /etc/network/interfaces as you like. The
networking.service is used to run ifup and ifdown to configure and
reconfigure the network with what's in /etc/network/interfaces.

Re: new install: configuring ethernet strangeness

[John Covici]

I did not get that tasksel at all, at the end of the install I had 12
choices, 11 was ssh server and 12 was standard system components and
by mistake I chose 12.  I cannot use the gui, I need speech to read
the screen and I don't want all that bloat running on a voip server.
What if I just put a stanza in /etc/network/interfaces and get rid of
network manager?

On Sat, 18 Jun 2022 07:04:47 -0400,
Andrew M.A. Cater wrote:
> 
> On Sat, Jun 18, 2022 at 04:21:35AM -0400, John Covici wrote:
> > Hi.  I just installed Debian Bullseye on a refurbished computer which
> > I am going to use as a voip server.  Now, due to my ignorance, at the
> > very end of the install, I selected to use #12 which said standard
> > system items.
> > 
> > Well, to my horror, I got gnome with all its dependencies.  I ran
> > apt-get and purged all the gnome items.  However, my outgoing
> > connection instead of being in /etc/network/interfaces is now managed
> > by network-manager.  I don't want to use the gui, but there seems to
> > be no good way to configure the connection, should I need to do so.
> > /etc/systemd/network is  empty.
> > 
> > So, how can I either get back to /etc/network/interfaces or somehow
> > manage the existing connection which is buried in
> > /etc/NetworkManager/system-connections/  and is readable, but I could
> > never change it.
> > 
> > Thanks in advance for any suggestions.
> > 
> > -- 
> > Your life is like a penny.  You're going to lose it.  The question is:
> > How do
> > you spend it?
> > 
> >  John Covici wb2una
> >  cov...@ccs.covici.com
> >
> 
> Hi John,
> 
> I find that nmtui - the text interface is quite useful. It is persistent - 
> configuration will stick around. 
> 
> For anybody else: if you really don't want a GUI at all: if you deselect
> both GNOME and Debian desktop components in the tasksel step of the Debian
> installer then you should get no GUI components. If you then explicitly
> select standard install components lower down in tasksel, you will get
> some X Windows libraries but you will end up with no GUI and no desktop
> environment as far as I recollect. It's necessary to uncheck both the 
> Debian desktop environment AND the default of GNOME which is selected.
> 
> All the very best, as ever,
> 
> Andy Cater 
> 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: new install: configuring ethernet strangeness

[Andrew M.A. Cater]

On Sat, Jun 18, 2022 at 04:21:35AM -0400, John Covici wrote:
> Hi.  I just installed Debian Bullseye on a refurbished computer which
> I am going to use as a voip server.  Now, due to my ignorance, at the
> very end of the install, I selected to use #12 which said standard
> system items.
> 
> Well, to my horror, I got gnome with all its dependencies.  I ran
> apt-get and purged all the gnome items.  However, my outgoing
> connection instead of being in /etc/network/interfaces is now managed
> by network-manager.  I don't want to use the gui, but there seems to
> be no good way to configure the connection, should I need to do so.
> /etc/systemd/network is  empty.
> 
> So, how can I either get back to /etc/network/interfaces or somehow
> manage the existing connection which is buried in
> /etc/NetworkManager/system-connections/  and is readable, but I could
> never change it.
> 
> Thanks in advance for any suggestions.
> 
> -- 
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
> 
>  John Covici wb2una
>  cov...@ccs.covici.com
>

Hi John,

I find that nmtui - the text interface is quite useful. It is persistent - 
configuration will stick around. 

For anybody else: if you really don't want a GUI at all: if you deselect
both GNOME and Debian desktop components in the tasksel step of the Debian
installer then you should get no GUI components. If you then explicitly
select standard install components lower down in tasksel, you will get
some X Windows libraries but you will end up with no GUI and no desktop
environment as far as I recollect. It's necessary to uncheck both the 
Debian desktop environment AND the default of GNOME which is selected.

All the very best, as ever,

Andy Cater 

Re: new install: configuring ethernet strangeness

[john doe]

On 6/18/2022 10:21 AM, John Covici wrote:

Hi.  I just installed Debian Bullseye on a refurbished computer which
I am going to use as a voip server.  Now, due to my ignorance, at the
very end of the install, I selected to use #12 which said standard
system items.

Well, to my horror, I got gnome with all its dependencies.  I ran
apt-get and purged all the gnome items.  However, my outgoing
connection instead of being in /etc/network/interfaces is now managed
by network-manager.  I don't want to use the gui, but there seems to
be no good way to configure the connection, should I need to do so.
/etc/systemd/network is  empty.

So, how can I either get back to /etc/network/interfaces or somehow
manage the existing connection which is buried in
/etc/NetworkManager/system-connections/  and is readable, but I could
never change it.

Thanks in advance for any suggestions.



If I may, redo the install from scratch and use '11' to only install
'standard system items' ! :)

To answer your question specifically, you can 'purge' networkmanager
with something like:

$ apt-get --autoremove purge 

--
John Doe

new install: configuring ethernet strangeness

[John Covici]

Hi.  I just installed Debian Bullseye on a refurbished computer which
I am going to use as a voip server.  Now, due to my ignorance, at the
very end of the install, I selected to use #12 which said standard
system items.

Well, to my horror, I got gnome with all its dependencies.  I ran
apt-get and purged all the gnome items.  However, my outgoing
connection instead of being in /etc/network/interfaces is now managed
by network-manager.  I don't want to use the gui, but there seems to
be no good way to configure the connection, should I need to do so.
/etc/systemd/network is  empty.

So, how can I either get back to /etc/network/interfaces or somehow
manage the existing connection which is buried in
/etc/NetworkManager/system-connections/  and is readable, but I could
never change it.

Thanks in advance for any suggestions.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: about 10th new install of bullseye

[Charles Kroeger]

replace the GPU card Gene it's kaput.

C

Re: about 10th new install of bullseye

[David Wright]

On Sun 20 Feb 2022 at 07:47:57 (+0100), john doe wrote:
> On 2/19/2022 9:03 PM, David Wright wrote:
> > On Fri 18 Feb 2022 at 20:46:03 (-0800), Gene Heskett wrote:
> > > Since last post, I found the install logs, and BRLTTY is listed in the 
> > > hardware file, as if its a mobo feature. And reading the DIY Guid from 
> > > Asus, there is a tools menu where some stiff that is not list, can be 
> > > controlled so the next time it forces me to reboot I will check that 
> > > menu. There is not any mention of brltty in the whole 100+ pages of the 
> > > book.  But its listed like this in the hardware-resources file:
> > > /proc/bus/input/devices: I: Bus= Vendor= Product= Version=
> > > /proc/bus/input/devices: N: Name="BRLTTY 6.3 Linux Screen Driver Keyboard"
> > > /proc/bus/input/devices: P: Phys=pid-221/brltty/11
> > > /proc/bus/input/devices: S: Sysfs=/devices/virtual/input/input14
> > > /proc/bus/input/devices: U: Uniq=
> > > /proc/bus/input/devices: H: Handlers=sysrq kbd event9
> > > /proc/bus/input/devices: B: PROP=0
> > > /proc/bus/input/devices: B: EV=13
> > > /proc/bus/input/devices: B: KEY=40207 ffc03078f800d2a9 
> > > f2beffdfffef fffe
> > > 
> > > Does that look like its part of the mobo, and might be disable-able in 
> > > the bios->tools menu, which is otherwise ignored in the users DIY 
> > > manual???  In which case it might solve my problem, but would involve yet 
> > > another install just to get the installer to get rid of it. IDK.
> 
> Given that you have access to the installer log and are able to
> reinstall, you should open a ticket with your issue.
> Having an issue fixed will help you and the community.

According to https://lists.debian.org/debian-user/2022/02/msg00684.html
the installer log isn't available. I don't know why.

"[Me:] If you're talking about the syslog that ends up in
/var/log/installer/, big deal. For verbosity, [ … ]

"[Gene:] Not THAT syslog, which isn't there, but its with /var/log/syslog, the 
main deal."

Cheers,
David.

Re: about 10th new install of bullseye

[john doe]

On 2/19/2022 9:03 PM, David Wright wrote:

On Fri 18 Feb 2022 at 20:46:03 (-0800), Gene Heskett wrote:

Since last post, I found the install logs, and BRLTTY is listed in the hardware 
file, as if its a mobo feature. And reading the DIY Guid from Asus, there is a 
tools menu where some stiff that is not list, can be controlled so the next 
time it forces me to reboot I will check that menu. There is not any mention of 
brltty in the whole 100+ pages of the book.  But its listed like this in the 
hardware-resources file:
/proc/bus/input/devices: I: Bus= Vendor= Product= Version=
/proc/bus/input/devices: N: Name="BRLTTY 6.3 Linux Screen Driver Keyboard"
/proc/bus/input/devices: P: Phys=pid-221/brltty/11
/proc/bus/input/devices: S: Sysfs=/devices/virtual/input/input14
/proc/bus/input/devices: U: Uniq=
/proc/bus/input/devices: H: Handlers=sysrq kbd event9
/proc/bus/input/devices: B: PROP=0
/proc/bus/input/devices: B: EV=13
/proc/bus/input/devices: B: KEY=40207 ffc03078f800d2a9 f2beffdfffef 
fffe

Does that look like its part of the mobo, and might be disable-able in the 
bios->tools menu, which is otherwise ignored in the users DIY manual???  In 
which case it might solve my problem, but would involve yet another install just 
to get the installer to get rid of it. IDK.




Given that you have access to the installer log and are able to
reinstall, you should open a ticket with your issue.
Having an issue fixed will help you and the community.

--
John Doe

Re: about 10th new install of bullseye

[gene heskett]

On Saturday, February 19, 2022 6:59:52 PM EST David Christensen wrote:
> On 2/18/22 22:15, Felix Miata wrote:
> > David Christensen composed on 2022-02-18 21:38 (UTC-0800):
> >> 4.  Do the simplest install of the OS of choice onto the SSD, using
> >> BIOS, MBR, and partitioning the OS drive such that the system image
> >> fits onto "16 GB" devices with room to spare -- 1 GB ext4 boot, 1
> >> GB encrypted swap, 12 GB encrypted ext4 root.
> > 
> > 1 + 1 + 12 = 14. Does the remaining 2 remain unallocated?
> 
> Yes -- to allow for "16 GB" devices with differing block counts.
> 
> 
> David
> 
> .
Precisely.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: about 10th new install of bullseye

[gene heskett]

On Friday, February 18, 2022 3:19:43 PM EST David Wright wrote:
> On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> > Two problems:
> > 
> > terminals went funkity late tuesday, spent Wed-Thu trying to reboot,
> > would not go beyond the 15 second mark rebooting. Finally ran the
> > net installer in rescue mode, copied my 122gb /home dir, on a 1.9T
> > raid10 to a different drive and reinstalled, then copied it back,
> > but kmail refuses to use the copied back data so I'm using FF to
> > post this.
> No idea what funkity means, nor what is significant about 15 seconds
> when booting. I have systems that boot in <3.5 seconds and other that
> take nearly a minute. Nor am I sure what's special about /home with
> respect to booting — it should have no role.
> 
> > I also need to get totally, absolutely rid of brltty, its driving me
> > berzerk with its incessant muttering in a voice as bandwidth
> > limited, or worse, than a cell phone. Understandable maybe 5% of the
> > time. I purposely did NOT even visit those pieces of the installer
> > for fear it would be enabled, because even though killed by removing
> > brltty in the previous install, 90% of the syslog was errors because
> > it couldn't use brltty. But I got it anyway.  So how do it get rid
> > of it without it tearing down the system with its copius error
> > screaming?
> Um, perhaps https://lists.debian.org/debian-user/2019/05/msg01001.html
> 

At 87 yo, you're expecting me to remember a post I made, what, 3 years 
ago? But its pretty close to exactly it. But I still don't recall if I 
unplugged the adapter that time, and by now there is probably at least 
one more, maybe two in my usb tree.

> Cheers,
> David.
> 
> .


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: about 10th new install of bullseye

[David Christensen]

On 2/18/22 22:15, Felix Miata wrote:

David Christensen composed on 2022-02-18 21:38 (UTC-0800):


4.  Do the simplest install of the OS of choice onto the SSD, using
BIOS, MBR, and partitioning the OS drive such that the system image fits
onto "16 GB" devices with room to spare -- 1 GB ext4 boot, 1 GB
encrypted swap, 12 GB encrypted ext4 root.


1 + 1 + 12 = 14. Does the remaining 2 remain unallocated?



Yes -- to allow for "16 GB" devices with differing block counts.


David

Re: about 10th new install of bullseye

[David Wright]

On Fri 18 Feb 2022 at 20:46:03 (-0800), Gene Heskett wrote:
> Since last post, I found the install logs, and BRLTTY is listed in the 
> hardware file, as if its a mobo feature. And reading the DIY Guid from Asus, 
> there is a tools menu where some stiff that is not list, can be controlled so 
> the next time it forces me to reboot I will check that menu. There is not any 
> mention of brltty in the whole 100+ pages of the book.  But its listed like 
> this in the hardware-resources file:
> /proc/bus/input/devices: I: Bus= Vendor= Product= Version= 
> /proc/bus/input/devices: N: Name="BRLTTY 6.3 Linux Screen Driver Keyboard" 
> /proc/bus/input/devices: P: Phys=pid-221/brltty/11 
> /proc/bus/input/devices: S: Sysfs=/devices/virtual/input/input14 
> /proc/bus/input/devices: U: Uniq= 
> /proc/bus/input/devices: H: Handlers=sysrq kbd event9  
> /proc/bus/input/devices: B: PROP=0 
> /proc/bus/input/devices: B: EV=13 
> /proc/bus/input/devices: B: KEY=40207 ffc03078f800d2a9 f2beffdfffef 
> fffe
> 
> Does that look like its part of the mobo, and might be disable-able in the 
> bios->tools menu, which is otherwise ignored in the users DIY manual???  In 
> which case it might solve my problem, but would involve yet another install 
> just to get the installer to get rid of it. IDK.

I have no idea. You might try running hwinfo repeatedly with different
plugs pulled out. I don't have access to your USB tree to see what's
there, but I assume something is describing itself as a BRLTTY.

I don't see anything here that has P: Phys=pid-221. I do know
that PID Controllers are used to run motors, which might help.
You run motors, and I've read that some braille machines use
motors to drive the bumps, so that might be a source of
confusion when probing the hardware. I guess that's something
you tackle with modules.alias, or udev rules, or whatever,
depending on how your system configures its devices.

Cheers,
David.

Re: about 10th new install of bullseye

[Curt]

On 2022-02-18, Andy Smith  wrote:
> Hello,
>
> On Fri, Feb 18, 2022 at 07:41:01PM +, Andrew M.A. Cater wrote:
>> In something of 150 or more installs of bullseye - we do a bunch with
>> each release of images with a point release - I don't think I've ever
>> seen brltty installed "by accident" so I'd love to know exactly what you
>> do do each time.
>
> It is really bizarre that this keeps happening to Gene and I can
> only think it is, as you say, something to do with the serial
> devices he has connected at install time.

In a long-ago thread we speculated Gene had an ft232 connected to his
machine, which was mistaken for a refreshable braille display and so
brought in brltty as a consequence. 

> Will the installer logs give any hint as to why brltty gets
> installed? If so perhaps he could try saving those before letting
> the installer reboot, and put them somewhere for us to see.
>
> Cheers,
> Andy
>


-- 

Re: about 10th new install of bullseye

[Andrew M.A. Cater]

Hi Gene,

If this was someone calling you from a TV station saying they had a TV
transmitter that was varying in power output - you'd have a mental checklist.
You'd get down there, perhaps schedule some sort of power down / reduced
power operation and then you'd check - power supplies, feeder cables, hot
spots on cables - whatever. Divide and conquer- working back to a baseline
of known working conditions and eliminating causes.

My suggestion to you of a reinstall is partly designed to get you out of this
"X happens, I did Y, now I've got Z" - to get to a known initial state.

Take out all the serial converters to UPS, lathe and so on. Wireless keyboard
doesn't present as serial in the same way that brltty does - if it did, I'd
have brltty with every install on this laptop.

Copy off your home directory as you did before - maybe using tar.gz and 
preserving permissions. Start with the .iso that includes firmware - the 
unofficial one.

Build back slowly - do an expert text mode install if you can. Then add your
Trinity desktop - I don't think any of us can help you there, since we don't
run trinity.

Check and you should find that brltty isn't installed at all. Then re-add 
thingsgradually until you have the working system you want. Document it - write 
down
the steps you take / copy configuration files you change.

That will also reveal logging / login slowdowns or whatever caused by 
individual devices as you add them back. Keep a list as you go.

That's the counsel of perfection: alternatively:

apt rdepends brltty gives me:

me@mymachine:~$ apt rdepends brltty
brltty
Reverse Depends:
  Suggests: speechd-el (>= 3.7.2)
  Depends: brltty-espeak (= 6.3+dfsg-1+deb11u1)
  Suggests: orca
  Depends: brltty-x11 (= 6.3+dfsg-1+deb11u1)
  Depends: brltty-speechd (= 6.3+dfsg-1+deb11u1)
  Depends: brltty-flite (= 6.3+dfsg-1+deb11u1)

You could try apt-get remove (or equivalent) on each of those packages and
see if that clears it. I _know_ this is frustrating as all get out for you
but a clear approach, written down so that you can remember where you got
to will be very helpful.

If all else fails, you can then share it with the list and say "I got to
step X with no problems, then Y happened - help me out here" and we'll 
have some better idea. We all jib at you for being vague/not indluding
details but otherwise it is all just guesswork for the usual folk that 
hang out here.

All the very best, as ever,

Andy Cater

Re: about 10th new install of bullseye

[Felix Miata]

David Christensen composed on 2022-02-18 21:38 (UTC-0800):

> 4.  Do the simplest install of the OS of choice onto the SSD, using 
> BIOS, MBR, and partitioning the OS drive such that the system image fits 
> onto "16 GB" devices with room to spare -- 1 GB ext4 boot, 1 GB 
> encrypted swap, 12 GB encrypted ext4 root.

1 + 1 + 12 = 14. Does the remaining 2 remain unallocated?
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: about 10th new install of bullseye

[David Christensen]

On 2/18/22 09:15, Gene Heskett wrote:

Two problems:


terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would not 
go beyond the 15 second mark rebooting. Finally ran the net installer in rescue 
mode, copied my 122gb /home dir, on a 1.9T raid10 to a different drive and 
reinstalled, then copied it back, but kmail refuses to use the copied back data 
so I'm using FF to post this.


I also need to get totally, absolutely rid of brltty, its driving me berzerk 
with its incessant muttering in a voice as bandwidth limited, or worse, than a 
cell phone. Understandable maybe 5% of the time. I purposely did NOT even visit 
those pieces of the installer for fear it would be enabled, because even though 
killed by removing brltty in the previous install, 90% of the syslog was errors 
because it couldn't use brltty. But I got it anyway.  So how do it get rid of 
it without it tearing down the system with its copius error screaming?


Thanks for any advice on these two fronts.


Cheers, Gene



On 2/18/22 15:38, Gene Heskett wrote:
> I'm on web mail using FF, which does not quote worth a damn. My "usb 
tree" looks like a weeping willow and contains several devices that 
answer to serial protocols. Both this keyboard and this mouse are 
wireless, and speak serial.  So how am I supposed to install with no 
keyboard?

>
>
> Interesting question that.
>
>
> Thanks, Cheers Gene


On 2/18/22 18:13, Gene Heskett wrote:
> On Fri, 18 Feb, 2022 at 7:41 PM, Greg Wooledge  wrote:

>> But what are the *actual* symptoms?  What did Gene see?  What did he
>> try, to troubleshoot, and what results did he get?
>
>
>
> Exactly what I wrote Greg, the boot stops at the 15 second mark, 
forever. I let it set there once for several hours while I caught some 
shuteye.

>
>
> Repeated at least 20 times.
>
>
>
> Putting the install dvd in that drive, and selecting rescue mode, 
works and I was able to make a backup of /home. Then I reinstalled. And 
on the reboot after the install this PITA of a blast of unintelligible 
noise per keystroke was back and I did not go anywhere near those menu 
item for this install.

>
>
>
>> These are basic questions that someone with Gene's level of experience
>> shouldn't need to be asked.
>
>
>
> Maybe so but I also getting upset with the feigned ignorance of what 
I type you won't believe. I said it stopped at about 15 seconds and I 
don't understand your lack of comprehension of the word "stopped". At 
that point, the only thing that worked was the front panel of this 30" 
towers reset button, or after a delay, the power button.

>
>
> Right now I've removed brltty and its api library which stops he 
racket of unintelligible sound, but my syslog is growing by abut 6 lines 
of errors per keystroke because brltty can't be found, or about every 4 
or 5 seconds even if the keyboard isn't in use.

>
> I need to find a way to remove this stuff w/o eviscerating half the 
system with its dependencies. Respin the installer for 11-4 if needed 
but this needs fixed.

>
>
>
> I'd also bet you a six pack of suds it won't reboot right now because 
I have removed brltty, and that IS the 15 second showstopper. But if my 
theory is correct, it will also add to the reinstall count which is 
already annoyingly high. Which with this system means at least a day to 
do it.

>
>
> Give us back stretch, once the install was fixed so it had 
networking, it just worked, till hell froze over.

>
>
> Oh, since we're on the subject, how do I put an option on the kernel 
load line,(in grub.cfg) to make very noisy debugging so the next time I 
have to reboot, I can see exactly what stopped it.  That would be a 
great help.

>
>
>
> Thanks Greg, take care and stay well.
>
>
> Cheers Gene


I recall that you have several computers, that your hobby is using Linux 
for CNC woodworking, and that you modify the OS's significantly and/or 
install specialized, non-Debian software.



I have found that when I install too much software, when I put 
non-Debian software on a Debian computer, and/or when I make too many 
changes to the OS and/or software, that the computer becomes unstable.



I have found it useful to spread storage and functionality across 
several computers, to limit the scope of disasters and to facilitate 
recovery.  These are the three key computers at my site:


1.  Primary workstation.

2.  Live server (Samba and SSH/CVS).

3.  Backup/ archive/ image/ replication server.


For Debian and FreeBSD machines, including the above, I install the OS 
as follows:


1.  Disconnect all hard disk drives, solid-state drives, USB flash 
drives, SDHC cards, etc..


2.  Disconnect all external devices from the computer except a keyboard, 
a mouse, a monitor, and the network connection (servers and desktops), 
or the network connection (laptops).


3.  Install a blank SSD.  Ensure that it is the first device node when 
the installer runs (e.g. /dev/sda).


4.  Do the simplest install of the OS of choice onto the SSD, 

Re: about 10th new install of bullseye

[Gene Heskett]

On Fri, 18 Feb, 2022 at 10:55 PM, David Wright  wrote:
 

To: debian-user@lists.debian.org
On Fri 18 Feb 2022 at 18:37:01 (-0800), Gene Heskett wrote:
> On Fri, 18 Feb, 2022 at 9:11 PM, David Wright 
> mailto:deb...@lionunicorn.co.uk>> wrote:
> On Fri 18 Feb 2022 at 19:48:40 (-0500), Cindy Sue Causey wrote:

> > That presents a detail that's not clear on Gene's case. Is the
> > computer just stopping and standing at that screen,
> 
> Exactly — and if it does, what's printed, and are you aware of
> anything that might be missing. Or does it reboot. Or is it still
> running, but writing to one of the many serial connections?
> 
> > or is it shutting
> > off? Mine shuts off.
> 
> And mine stops, period.

Adding "period" is no help. "Stop", on its own, is just so ambiguous.
What exactly stops, the process — or the computer.

In real life, we use the circumstances to decide on the meaning.
If I reported that I "stopped the car" because I saw a ball rolling
into the road, you'd assume I didn't cut the engine. If I said it
was because I saw a dust-devil barrelling down the road, you'd
assume I stopped both the car and engine.

> keyboard dead after reporting its there if I touch a key. once.

Again, I have no idea what this means. None of my keyboards has
ever reported anything, to my knowledge.

> No further response to anything but the reset button on the front of this 
> huge tower.
> 
> Theory is its looking for brltty and will not proceed without it. So until 
> that linkage is found and removed, I can't reboot w/o doing yet another 
> install right now.
> 
> It has to be removed entirely before I can reboot again.

Ah, is this because you nuked it (whatever we understand by
the term "nuked")?

If your machine is utterly unable to avoid installing it, perhaps
you'll have to read its documentation in a little more depth and
learn how to prevent it from finding a device to talk to.

Or can you blacklist the snd modules? What do you use sound for
on this computer? Is it essential for its task, which I assume
is something to do with a lathe? Or are you still playing videos,
logging in to your bank, and machining stuff, all on the same
computer? (I realise that's a loaded question.)

Cheers,
David.



yes. Just not all at the same time.


Since last post, I found the install logs, and BRLTTY is listed in the hardware 
file, as if its a mobo feature. And reading the DIY Guid from Asus, there is a 
tools menu where some stiff that is not list, can be controlled so the next 
time it forces me to reboot I will check that menu. There is not any mention of 
brltty in the whole 100+ pages of the book.  But its listed like this in the 
hardware-resources file:
/proc/bus/input/devices: I: Bus= Vendor= Product= Version= 
/proc/bus/input/devices: N: Name="BRLTTY 6.3 Linux Screen Driver Keyboard" 
/proc/bus/input/devices: P: Phys=pid-221/brltty/11 
/proc/bus/input/devices: S: Sysfs=/devices/virtual/input/input14 
/proc/bus/input/devices: U: Uniq= 
/proc/bus/input/devices: H: Handlers=sysrq kbd event9  
/proc/bus/input/devices: B: PROP=0 
/proc/bus/input/devices: B: EV=13 
/proc/bus/input/devices: B: KEY=40207 ffc03078f800d2a9 f2beffdfffef 
fffe



Does that look like its part of the mobo, and might be disable-able in the 
bios->tools menu, which is otherwise ignored in the users DIY manual???  In 
which case it might solve my problem, but would involve yet another install 
just to get the installer to get rid of it. IDK.

Re: about 10th new install of bullseye

[rhkramer]

On Friday, February 18, 2022 09:14:00 PM Greg Wooledge wrote:
> On Fri, Feb 18, 2022 at 08:08:21PM -0600, David Wright wrote:
> > I'm not sure what's eyebrow-raising about 122GB under /home.
> 
> unicorn:~$ df -h /home
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/sda823G   17G  5.0G  78% /home

I want to play to:

rhk@s19:/usr/share/man$ df -h /home
Filesystem  Size  Used Avail Use% Mounted on
/dev/sdb12  1.9G  1.3G  489M  73% /home

Re: about 10th new install of bullseye

[David Wright]

On Fri 18 Feb 2022 at 18:37:01 (-0800), Gene Heskett wrote:
> On Fri, 18 Feb, 2022 at 9:11 PM, David Wright  
> wrote:
> On Fri 18 Feb 2022 at 19:48:40 (-0500), Cindy Sue Causey wrote:

> > That presents a detail that's not clear on Gene's case. Is the
> > computer just stopping and standing at that screen,
> 
> Exactly — and if it does, what's printed, and are you aware of
> anything that might be missing. Or does it reboot. Or is it still
> running, but writing to one of the many serial connections?
> 
> > or is it shutting
> > off? Mine shuts off.
> 
> And mine stops, period.

Adding "period" is no help. "Stop", on its own, is just so ambiguous.
What exactly stops, the process — or the computer.

In real life, we use the circumstances to decide on the meaning.
If I reported that I "stopped the car" because I saw a ball rolling
into the road, you'd assume I didn't cut the engine. If I said it
was because I saw a dust-devil barrelling down the road, you'd
assume I stopped both the car and engine.

> keyboard dead after reporting its there if I touch a key. once.

Again, I have no idea what this means. None of my keyboards has
ever reported anything, to my knowledge.

> No further response to anything but the reset button on the front of this 
> huge tower.
> 
> Theory is its looking for brltty and will not proceed without it. So until 
> that linkage is found and removed, I can't reboot w/o doing yet another 
> install right now.
> 
> It has to be removed entirely before I can reboot again.

Ah, is this because you nuked it (whatever we understand by
the term "nuked")?

If your machine is utterly unable to avoid installing it, perhaps
you'll have to read its documentation in a little more depth and
learn how to prevent it from finding a device to talk to.

Or can you blacklist the snd modules? What do you use sound for
on this computer? Is it essential for its task, which I assume
is something to do with a lathe? Or are you still playing videos,
logging in to your bank, and machining stuff, all on the same
computer? (I realise that's a loaded question.)

Cheers,
David.

Re: about 10th new install of bullseye

[David Wright]

On Fri 18 Feb 2022 at 21:18:32 (-0500), The Wanderer wrote:
> On 2022-02-18 at 21:14, Greg Wooledge wrote:
> > On Fri, Feb 18, 2022 at 08:08:21PM -0600, David Wright wrote:
> >
> >> I'm not sure what's eyebrow-raising about 122GB under /home.
> > 
> > unicorn:~$ df -h /home
> > Filesystem  Size  Used Avail Use% Mounted on
> > /dev/sda823G   17G  5.0G  78% /home
> 
> aorta:~$ df -h /home/
> Filesystem   Size  Used Avail Use% Mounted on
> /dev/mapper/vg_data_aorta-lv_home_aorta   11T  5.6T  4.4T  57% /home
> 
> Though to be fair that's (part of) an... 8-drive?... RAID-6 array, and
> this system's storage capacities are *utterly ridiculous* for most
> consumer purposes.

# ssh -X wren
Linux wren 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Feb 18 14:20:22 2022 from 192.168.1.14
wren 20:54:02 ~# ls -GRagl /home/
/home/:
total 12
drwxr-xr-x  3 4096 Jan 31 19:30 .
drwxr-xr-x 20 4096 Feb 14 22:53 ..
-rw-r--r--  10 Jan 31 19:30 0
drwxr-xr-x  2 4096 Jan 31 19:30 admin

/home/admin:
total 16
drwxr-xr-x 2 4096 Jan 31 19:30 .
drwxr-xr-x 3 4096 Jan 31 19:30 ..
-rw-r--r-- 1  680 Jan 28 12:38 .bashrc
-rw-r--r-- 1  807 Jan  1 11:29 .profile
wren 20:54:11 ~# 

by way of contrast!

Cheers,
David.

Re: about 10th new install of bullseye

[Gene Heskett]

On Fri, 18 Feb, 2022 at 9:30 PM, David Wright  wrote:
 

To: debian-user@lists.debian.org
On Fri 18 Feb 2022 at 18:13:02 (-0800), Gene Heskett wrote:
> On Fri, 18 Feb, 2022 at 7:41 PM, Greg Wooledge 
> mailto:g...@wooledge.org>> wrote:
>  
> 
> To: debian-user@lists.debian.org
> On Fri, Feb 18, 2022 at 07:21:19PM -0500, Felix Miata wrote:
> > David Wright composed on 2022-02-18 14:19 (UTC-0600):
> > 
> > > On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> > 
> > >> Two problems:
> > 
> > >> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, 
> > >> would not go beyond the 15 second mark rebooting. Finally ran the net 
> > >> installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to 
> > >> a different drive and reinstalled, then copied it back, but kmail 
> > >> refuses to use the copied back data so I'm using FF to post this.
> > 
> > > No idea what funkity means,
> > 
> > nuts, cuckoo, fubar, whacky, loopy aka abnormal
> 
> But what are the *actual* symptoms?  What did Gene see?  What did he
> try, to troubleshoot, and what results did he get?
> 
> 
> 
> Exactly what I wrote Greg, the boot stops at the 15 second mark, forever. I 
> let it set there once for several hours while I caught some shuteye.

Typing /stop in my MUA shows that the line immediately above this one
contains the first occurrence of the word "stop" in this post.

> Oh, since we're on the subject, how do I put an option on the kernel load 
> line,(in grub.cfg) to make very noisy debugging so the next time I have to 
> reboot, I can see exactly what stopped it.  That would be a great help.

Add the string   systemd.show_status=true



Added to the default grub.cfg profile, thank you


Removing   quiet   might get just too verbose, because I believe
you can no longer scroll back like in the olden days.



What I have reported was without the quiet argument, which I should have noted.

Cheers,
David.

Cheers Gene.

Re: about 10th new install of bullseye

[Gene Heskett]

On Fri, 18 Feb, 2022 at 9:11 PM, David Wright  wrote:
 

To: debian-user@lists.debian.org
On Fri 18 Feb 2022 at 19:48:40 (-0500), Cindy Sue Causey wrote:
> On 2/18/22, Felix Miata mailto:mrma...@earthlink.net>> 
> wrote:
> > David Wright composed on 2022-02-18 14:19 (UTC-0600):
> >> On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> >
> >>> Two problems:
> >
> >>> terminals went funkity late tuesday, spent Wed-Thu trying to reboot,
> >>> would not go beyond the 15 second mark rebooting. Finally ran the net
> >>> installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to
> >>> a different drive and reinstalled, then copied it back, but kmail refuses
> >>> to use the copied back data so I'm using FF to post this.
> >
> >> No idea what funkity means,
> >
> > nuts, cuckoo, fubar, whacky, loopy aka abnormal
> >
> >> nor what is significant about 15 seconds
> >> when booting.
> >
> > Boot messages scroll on vtty 1 normally for about 15 seconds, then quit.
> 
> That's what I understood, too. Mine's occasionally doing something
> like that. It seems to be tied to CPU temperatures (overheating).
> 
> It's really kind of weird. It's for that first few seconds of booting
> where it's running through a checkup before those boot messages begin
> appearing.

What I call the POST? Yes, well in the olden days, when we had real
CRTs, and "everything" ran at VGA resolution, you could sit back for
a minute and watch the whole light show: Graphics card, BIOS, POST,
Lilo, Kernel, and all the dmesg stuff, with the odd screen clearance
but no noticeable change in mode. (I used to scroll back and cut and
paste everything post-POST into an archived file.)

Nowadays, with these fancy flatscreens, each change in mode can lead
to a significant blank period (seconds) while it sorts itself out.

> When mine keeps flicking off like that, fanning it with a
> piece of paper gets it past that hump then it doesn't do it again.
> It's like something in the first stage is pushing the CPUs hard then
> it backs off once those messages start scrolling.

Do you mean that you hear the fan going at full speed? Yes, that's
quite normal AIUI, and seems very sensible: if nothing is monitoring
the temperature of the system, then running the fan is the failsafe state.

> That presents a detail that's not clear on Gene's case. Is the
> computer just stopping and standing at that screen,

Exactly — and if it does, what's printed, and are you aware of
anything that might be missing. Or does it reboot. Or is it still
running, but writing to one of the many serial connections?

> or is it shutting
> off? Mine shuts off.

Cheers,
David.


And mine stops, period. keyboard dead after reporting its there if I touch a 
key. once. No further response to anything but the reset button on the front of 
this huge tower.


Theory is its looking for brltty and will not proceed without it. So until that 
linkage is found and removed, I can't reboot w/o doing yet another install 
right now.


It has to be removed entirely before I can reboot again.

Re: about 10th new install of bullseye

[David Wright]

On Fri 18 Feb 2022 at 18:13:02 (-0800), Gene Heskett wrote:
> On Fri, 18 Feb, 2022 at 7:41 PM, Greg Wooledge  wrote:
>  
> 
> To: debian-user@lists.debian.org
> On Fri, Feb 18, 2022 at 07:21:19PM -0500, Felix Miata wrote:
> > David Wright composed on 2022-02-18 14:19 (UTC-0600):
> > 
> > > On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> > 
> > >> Two problems:
> > 
> > >> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, 
> > >> would not go beyond the 15 second mark rebooting. Finally ran the net 
> > >> installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to 
> > >> a different drive and reinstalled, then copied it back, but kmail 
> > >> refuses to use the copied back data so I'm using FF to post this.
> > 
> > > No idea what funkity means,
> > 
> > nuts, cuckoo, fubar, whacky, loopy aka abnormal
> 
> But what are the *actual* symptoms?  What did Gene see?  What did he
> try, to troubleshoot, and what results did he get?
> 
> 
> 
> Exactly what I wrote Greg, the boot stops at the 15 second mark, forever. I 
> let it set there once for several hours while I caught some shuteye.

Typing /stop in my MUA shows that the line immediately above this one
contains the first occurrence of the word "stop" in this post.

> Oh, since we're on the subject, how do I put an option on the kernel load 
> line,(in grub.cfg) to make very noisy debugging so the next time I have to 
> reboot, I can see exactly what stopped it.  That would be a great help.

Add the string   systemd.show_status=true

Removing   quiet   might get just too verbose, because I believe
you can no longer scroll back like in the olden days.

Cheers,
David.

Re: about 10th new install of bullseye

[The Wanderer]

On 2022-02-18 at 21:14, Greg Wooledge wrote:

> On Fri, Feb 18, 2022 at 08:08:21PM -0600, David Wright wrote:
>
>> I'm not sure what's eyebrow-raising about 122GB under /home.
> 
> unicorn:~$ df -h /home
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/sda823G   17G  5.0G  78% /home

aorta:~$ df -h /home/
Filesystem   Size  Used Avail Use% Mounted on
/dev/mapper/vg_data_aorta-lv_home_aorta   11T  5.6T  4.4T  57% /home

Though to be fair that's (part of) an... 8-drive?... RAID-6 array, and
this system's storage capacities are *utterly ridiculous* for most
consumer purposes.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: about 10th new install of bullseye

[Greg Wooledge]

On Fri, Feb 18, 2022 at 08:08:21PM -0600, David Wright wrote:
> I'm not sure what's eyebrow-raising about 122GB under /home.

unicorn:~$ df -h /home
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda823G   17G  5.0G  78% /home

Re: about 10th new install of bullseye

[David Wright]

On Fri 18 Feb 2022 at 19:48:40 (-0500), Cindy Sue Causey wrote:
> On 2/18/22, Felix Miata  wrote:
> > David Wright composed on 2022-02-18 14:19 (UTC-0600):
> >> On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> >
> >>> Two problems:
> >
> >>> terminals went funkity late tuesday, spent Wed-Thu trying to reboot,
> >>> would not go beyond the 15 second mark rebooting. Finally ran the net
> >>> installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to
> >>> a different drive and reinstalled, then copied it back, but kmail refuses
> >>> to use the copied back data so I'm using FF to post this.
> >
> >> No idea what funkity means,
> >
> > nuts, cuckoo, fubar, whacky, loopy aka abnormal
> >
> >> nor what is significant about 15 seconds
> >> when booting.
> >
> > Boot messages scroll on vtty 1 normally for about 15 seconds, then quit.
> 
> That's what I understood, too. Mine's occasionally doing something
> like that. It seems to be tied to CPU temperatures (overheating).
> 
> It's really kind of weird. It's for that first few seconds of booting
> where it's running through a checkup before those boot messages begin
> appearing.

What I call the POST? Yes, well in the olden days, when we had real
CRTs, and "everything" ran at VGA resolution, you could sit back for
a minute and watch the whole light show: Graphics card, BIOS, POST,
Lilo, Kernel, and all the dmesg stuff, with the odd screen clearance
but no noticeable change in mode. (I used to scroll back and cut and
paste everything post-POST into an archived file.)

Nowadays, with these fancy flatscreens, each change in mode can lead
to a significant blank period (seconds) while it sorts itself out.

> When mine keeps flicking off like that, fanning it with a
> piece of paper gets it past that hump then it doesn't do it again.
> It's like something in the first stage is pushing the CPUs hard then
> it backs off once those messages start scrolling.

Do you mean that you hear the fan going at full speed? Yes, that's
quite normal AIUI, and seems very sensible: if nothing is monitoring
the temperature of the system, then running the fan is the failsafe state.

> That presents a detail that's not clear on Gene's case. Is the
> computer just stopping and standing at that screen,

Exactly — and if it does, what's printed, and are you aware of
anything that might be missing. Or does it reboot. Or is it still
running, but writing to one of the many serial connections?

> or is it shutting
> off? Mine shuts off.

Cheers,
David.

Re: about 10th new install of bullseye

[Gene Heskett]

On Fri, 18 Feb, 2022 at 7:41 PM, Greg Wooledge  wrote:
 

To: debian-user@lists.debian.org
On Fri, Feb 18, 2022 at 07:21:19PM -0500, Felix Miata wrote:
> David Wright composed on 2022-02-18 14:19 (UTC-0600):
> 
> > On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> 
> >> Two problems:
> 
> >> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would 
> >> not go beyond the 15 second mark rebooting. Finally ran the net installer 
> >> in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different 
> >> drive and reinstalled, then copied it back, but kmail refuses to use the 
> >> copied back data so I'm using FF to post this.
> 
> > No idea what funkity means,
> 
> nuts, cuckoo, fubar, whacky, loopy aka abnormal

But what are the *actual* symptoms?  What did Gene see?  What did he
try, to troubleshoot, and what results did he get?



Exactly what I wrote Greg, the boot stops at the 15 second mark, forever. I let 
it set there once for several hours while I caught some shuteye.


Repeated at least 20 times.



Putting the install dvd in that drive, and selecting rescue mode, works and I 
was able to make a backup of /home. Then I reinstalled. And on the reboot after 
the install this PITA of a blast of unintelligible noise per keystroke was back 
and I did not go anywhere near those menu item for this install.



These are basic questions that someone with Gene's level of experience
shouldn't need to be asked.



Maybe so but I also getting upset with the feigned ignorance of what I type you 
won't believe. I said it stopped at about 15 seconds and I don't understand 
your lack of comprehension of the word "stopped". At that point, the only thing 
that worked was the front panel of this 30" towers reset button, or after a 
delay, the power button.


Right now I've removed brltty and its api library which stops he racket of 
unintelligible sound, but my syslog is growing by abut 6 lines of errors per 
keystroke because brltty can't be found, or about every 4 or 5 seconds even if 
the keyboard isn't in use.

I need to find a way to remove this stuff w/o eviscerating half the system with 
its dependencies. Respin the installer for 11-4 if needed but this needs fixed.



I'd also bet you a six pack of suds it won't reboot right now because I have 
removed brltty, and that IS the 15 second showstopper. But if my theory is 
correct, it will also add to the reinstall count which is already annoyingly 
high. Which with this system means at least a day to do it.


Give us back stretch, once the install was fixed so it had networking, it just 
worked, till hell froze over.


Oh, since we're on the subject, how do I put an option on the kernel load 
line,(in grub.cfg) to make very noisy debugging so the next time I have to 
reboot, I can see exactly what stopped it.  That would be a great help.



Thanks Greg, take care and stay well.


Cheers Gene

Re: about 10th new install of bullseye

[David Wright]

On Fri 18 Feb 2022 at 19:41:01 (+), Andrew M.A. Cater wrote:
> On Fri, Feb 18, 2022 at 09:15:50AM -0800, Gene Heskett wrote:
> > Two problems:
> > 
> > terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would 
> > not go beyond the 15 second mark rebooting. Finally ran the net installer 
> > in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different 
> > drive and reinstalled, then copied it back, but kmail refuses to use the 
> > copied back data so I'm using FF to post this.
> 
> Check permissions on spools etc - how did you copy your data out?
> A tar ball preserving permissions is also quite useful for this.
> Goodness, what do you keep to make your /home directory 122G?

I'm not sure what's eyebrow-raising about 122GB under /home.

$ dfree
Filesystem  IUse%  Type  1MB-blocksUsed  Avail  Use%  Mounted  on
/dev/sda4 19%  ext4   30830   26224¹   3016   90%  /
/dev/sda2   -  vfat 520   75142%  /boot/efi
/dev/dm-1  2%  ext4  428208  382990  23396   95%  /home
$ 

A large /home seems sufficient reason to mount it from a separate
partition. Then all you have to worry about when you reinstall is
which of your dotfiles do you let the fresh system get to see, and
which do you hide (in case they're causing problems).

¹ /var/cache/apt-cacher-ng/<2½ versions> occupies ~13GB.

Cheers,
David.

Re: about 10th new install of bullseye

[Cindy Sue Causey]

On 2/18/22, Felix Miata  wrote:
> David Wright composed on 2022-02-18 14:19 (UTC-0600):
>
>> On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
>
>>> Two problems:
>
>>> terminals went funkity late tuesday, spent Wed-Thu trying to reboot,
>>> would not go beyond the 15 second mark rebooting. Finally ran the net
>>> installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to
>>> a different drive and reinstalled, then copied it back, but kmail refuses
>>> to use the copied back data so I'm using FF to post this.
>
>> No idea what funkity means,
>
> nuts, cuckoo, fubar, whacky, loopy aka abnormal
>
>> nor what is significant about 15 seconds
>> when booting.
>
> Boot messages scroll on vtty 1 normally for about 15 seconds, then quit.


That's what I understood, too. Mine's occasionally doing something
like that. It seems to be tied to CPU temperatures (overheating).

It's really kind of weird. It's for that first few seconds of booting
where it's running through a checkup before those boot messages begin
appearing. When mine keeps flicking off like that, fanning it with a
piece of paper gets it past that hump then it doesn't do it again.
It's like something in the first stage is pushing the CPUs hard then
it backs off once those messages start scrolling.

That presents a detail that's not clear on Gene's case. Is the
computer just stopping and standing at that screen, or is it shutting
off? Mine shuts off. This might be an apples and oranges thing where I
typed a bunch of noise. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: about 10th new install of bullseye

[Greg Wooledge]

On Fri, Feb 18, 2022 at 07:21:19PM -0500, Felix Miata wrote:
> David Wright composed on 2022-02-18 14:19 (UTC-0600):
> 
> > On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> 
> >> Two problems:
> 
> >> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would 
> >> not go beyond the 15 second mark rebooting. Finally ran the net installer 
> >> in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different 
> >> drive and reinstalled, then copied it back, but kmail refuses to use the 
> >> copied back data so I'm using FF to post this.
> 
> > No idea what funkity means,
> 
> nuts, cuckoo, fubar, whacky, loopy aka abnormal

But what are the *actual* symptoms?  What did Gene see?  What did he
try, to troubleshoot, and what results did he get?

These are basic questions that someone with Gene's level of experience
shouldn't need to be asked.

Re: about 10th new install of bullseye

[Felix Miata]

David Wright composed on 2022-02-18 14:19 (UTC-0600):

> On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:

>> Two problems:

>> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would 
>> not go beyond the 15 second mark rebooting. Finally ran the net installer in 
>> rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different 
>> drive and reinstalled, then copied it back, but kmail refuses to use the 
>> copied back data so I'm using FF to post this.

> No idea what funkity means,

nuts, cuckoo, fubar, whacky, loopy aka abnormal

> nor what is significant about 15 seconds
> when booting.

Boot messages scroll on vtty 1 normally for about 15 seconds, then quit.

> I have systems that boot in <3.5 seconds and other that
> take nearly a minute. Nor am I sure what's special about /home with
> respect to booting — it should have no role.

It's about protecting user data against unexpected installation results.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: about 10th new install of bullseye

[David Wright]

On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> Two problems:
> 
> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would 
> not go beyond the 15 second mark rebooting. Finally ran the net installer in 
> rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different drive 
> and reinstalled, then copied it back, but kmail refuses to use the copied 
> back data so I'm using FF to post this.

No idea what funkity means, nor what is significant about 15 seconds
when booting. I have systems that boot in <3.5 seconds and other that
take nearly a minute. Nor am I sure what's special about /home with
respect to booting — it should have no role.

> I also need to get totally, absolutely rid of brltty, its driving me berzerk 
> with its incessant muttering in a voice as bandwidth limited, or worse, than 
> a cell phone. Understandable maybe 5% of the time. I purposely did NOT even 
> visit those pieces of the installer for fear it would be enabled, because 
> even though killed by removing brltty in the previous install, 90% of the 
> syslog was errors because it couldn't use brltty. But I got it anyway.  So 
> how do it get rid of it without it tearing down the system with its copius 
> error screaming?

Um, perhaps https://lists.debian.org/debian-user/2019/05/msg01001.html

Cheers,
David.

Re: about 10th new install of bullseye

[Andy Smith]

Hello,

On Fri, Feb 18, 2022 at 07:41:01PM +, Andrew M.A. Cater wrote:
> In something of 150 or more installs of bullseye - we do a bunch with
> each release of images with a point release - I don't think I've ever
> seen brltty installed "by accident" so I'd love to know exactly what you
> do do each time.

It is really bizarre that this keeps happening to Gene and I can
only think it is, as you say, something to do with the serial
devices he has connected at install time.

Will the installer logs give any hint as to why brltty gets
installed? If so perhaps he could try saving those before letting
the installer reboot, and put them somewhere for us to see.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: about 10th new install of bullseye

[Andrew M.A. Cater]

On Fri, Feb 18, 2022 at 09:15:50AM -0800, Gene Heskett wrote:
> Two problems:
> 
> 
> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would 
> not go beyond the 15 second mark rebooting. Finally ran the net installer in 
> rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different drive 
> and reinstalled, then copied it back, but kmail refuses to use the copied 
> back data so I'm using FF to post this.
> 
> 

Hi Gene 


Check permissions on spools etc - how did you copy your data out?
A tar ball preserving permissions is also quite useful for this.
Goodness, what do you keep to make your /home directory 122G?

> I also need to get totally, absolutely rid of brltty, its driving me berzerk 
> with its incessant muttering in a voice as bandwidth limited, or worse, than 
> a cell phone. Understandable maybe 5% of the time. I purposely did NOT even 
> visit those pieces of the installer for fear it would be enabled, because 
> even though killed by removing brltty in the previous install, 90% of the 
> syslog was errors because it couldn't use brltty. But I got it anyway.  So 
> how do it get rid of it without it tearing down the system with its copius 
> error screaming?
> 

Just a thought: apt rdepends brltty reveals a small number of things
that depend on it. Use apt-get / aptitude or whatever to remove these in
order.

I don't know _why_ you keep getting brltty installed - disconnect any
serial leads from this machine as a start. If you can't get brltty 
removed as above - copy your home directory off again and do a reinstall
with the minimum connected to your machine.

[The serial idea is because I seem to recall that if brltty finds a serial
connection active at install, it may assume there's a brltty installed.

In something of 150 or more installs of bullseye - we do a bunch with
each release of images with a point release - I don't think I've ever
seen brltty installed "by accident" so I'd love to know exactly what you
do do each time.

All the very best, as ever,

Andy Cater


> 
> Thanks for any advice on these two fronts.
> 
> 
> Cheers, Gene

about 10th new install of bullseye

[Gene Heskett]

Two problems:


terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would not 
go beyond the 15 second mark rebooting. Finally ran the net installer in rescue 
mode, copied my 122gb /home dir, on a 1.9T raid10 to a different drive and 
reinstalled, then copied it back, but kmail refuses to use the copied back data 
so I'm using FF to post this.


I also need to get totally, absolutely rid of brltty, its driving me berzerk 
with its incessant muttering in a voice as bandwidth limited, or worse, than a 
cell phone. Understandable maybe 5% of the time. I purposely did NOT even visit 
those pieces of the installer for fear it would be enabled, because even though 
killed by removing brltty in the previous install, 90% of the syslog was errors 
because it couldn't use brltty. But I got it anyway.  So how do it get rid of 
it without it tearing down the system with its copius error screaming?


Thanks for any advice on these two fronts.


Cheers, Gene

[Solved] (Was: Re: help new install debian via WiFi)

[황병희]

Eduardo M KALINOWSKI  writes:

> On 13/09/2021 09:45, 황병희 wrote:
>> Hellow! Eduardo^^^
>> Eduardo M KALINOWSKI  writes:
>> 
>>> Try the installer with non-free firmware, pretty much all Wi-Fi cards
>>> require non-free firmware:
>>> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
>> Wow you are my hero!
>> How can i input the file into *the usb stick*?
>> With no error, i did download firmware-11.0.0-amd64-netinst.iso.
>> (My file system is Chrome OS that have linux shell and commands)
>
> The same way you copied the other installed: just cp the file to the
> drive. Something like
>
> # cp firmware-11.0.0-amd64-netinst.iso /dev/sdX
>
> Substitute sdX for the device your USB drive gets assigned. Be sure to
> use the whole drive, not a partition.

Thank you very so much all guys!
Eduardo, Stanislav, Andrei, thanks thanks thanks!

Here are the last screenshots:
http://forum.ubuntu-kr.org/viewtopic.php?f=15=31119=130056=cbfeb3d3e0982466ae84f1b6bd42255a#p130056

Sincerely, Byung-Hee from South Korea

Re: help new install debian via WiFi

[Andrei POPESCU]

On Lu, 13 sep 21, 21:28:24, 황병희 wrote:
> 
> i have new another notebook that is thinkpad (not chromebook).
> and i have one usb stick.
> i downloaded mini.iso file.
> and i put mini.iso in usb stick as follow commands:
> 
> #+begin_src: sh
> $ sudo cp mini.iso /dev/sda1
> $ sudo sync
> #+end_src
> 
> then i did try to boot with usb stick on thinkpad notebook.
> 
> and that showed well the some configs such as lang/contry/keyboard
> but faild to detacting internet zone.
> that did to try searching some DHCP thing all the time.
> fail and fail and so on...
> 
> so i did open chromebook and Gnus.
> 
> How can i connect WiFi zone (not DHCP) at new install (Debian 11)?

Hello,

When you copied the mini.iso to the stick it should have created a FAT 
partition that you can use to provide the necessary firmware to the 
installer, e.g. this file:

https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/bullseye/current/firmware.tar.gz

Just unplug and replug the stick and the partition should show up.

Hope this help,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: help new install debian via WiFi

[Eduardo M KALINOWSKI]

On 13/09/2021 09:45, 황병희 wrote:

Hellow! Eduardo^^^

Eduardo M KALINOWSKI  writes:


Try the installer with non-free firmware, pretty much all Wi-Fi cards
require non-free firmware:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/


Wow you are my hero!
How can i input the file into *the usb stick*?

With no error, i did download firmware-11.0.0-amd64-netinst.iso.
(My file system is Chrome OS that have linux shell and commands)


The same way you copied the other installed: just cp the file to the 
drive. Something like


# cp firmware-11.0.0-amd64-netinst.iso /dev/sdX

Substitute sdX for the device your USB drive gets assigned. Be sure to 
use the whole drive, not a partition.



--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: help new install debian via WiFi

[황병희]

Hellow! Eduardo^^^

Eduardo M KALINOWSKI  writes:

> Try the installer with non-free firmware, pretty much all Wi-Fi cards
> require non-free firmware: 
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

Wow you are my hero!
How can i input the file into *the usb stick*?

With no error, i did download firmware-11.0.0-amd64-netinst.iso.
(My file system is Chrome OS that have linux shell and commands)

Thanks in advance,

Sincerely, Byung-Hee from South Korea

Re: help new install debian via WiFi

[Stanislav Vlasov]

2021-09-13 17:28 GMT+05:00, 황병희 :

> How can i connect WiFi zone (not DHCP) at new install (Debian 11)?

Try 
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/
It's help me on Lenovo netbook and many HP servers.

-- 
Stanislav

Re: help new install debian via WiFi

[Eduardo M KALINOWSKI]

On 13/09/2021 09:28, 황병희 wrote:

and i put mini.iso in usb stick as follow commands:

#+begin_src: sh
$ sudo cp mini.iso /dev/sda1


That should have been /dev/sda, but since you said the installer booted 
and started, I assume it's just a typo.



$ sudo sync
#+end_src

then i did try to boot with usb stick on thinkpad notebook.

and that showed well the some configs such as lang/contry/keyboard
but faild to detacting internet zone.
that did to try searching some DHCP thing all the time.
fail and fail and so on...

so i did open chromebook and Gnus.

How can i connect WiFi zone (not DHCP) at new install (Debian 11)?


Try the installer with non-free firmware, pretty much all Wi-Fi cards 
require non-free firmware: 
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/



--
'Back in the USSR' musica dos Beatles, por John Lenin e Ringo Stalin.

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

help new install debian via WiFi

[황병희]

hellow

i did buy new notebook thinkpad ryzen.
and there is samsung galaxy phone (android).
this phone is internet router of my home.

and i am writing letter another chromebook.
this chromebook have debian 11 under chrome os.
this debian 11 is easy to connect internet.
because chrome os is detecting WiFi auto with easy.

ok man again i have to say my work in progress.

i have new another notebook that is thinkpad (not chromebook).
and i have one usb stick.
i downloaded mini.iso file.
and i put mini.iso in usb stick as follow commands:

#+begin_src: sh
$ sudo cp mini.iso /dev/sda1
$ sudo sync
#+end_src

then i did try to boot with usb stick on thinkpad notebook.

and that showed well the some configs such as lang/contry/keyboard
but faild to detacting internet zone.
that did to try searching some DHCP thing all the time.
fail and fail and so on...

so i did open chromebook and Gnus.

How can i connect WiFi zone (not DHCP) at new install (Debian 11)?


Sincerely, Byung-Hee from South Korea

Re: Two questions as I prepare for a new install

[David Wright]

On Wed 09 Dec 2020 at 19:10:53 (+), Mark Fletcher wrote:
> On Mon, Dec 07, 2020 at 06:06:43PM -0700, Charles Curley wrote:
> > On Tue, 8 Dec 2020 00:00:54 + Mark Fletcher wrote:
> > 
> > > 1. Does anyone have any advice (or a link to offcial advice)
> > > regarding whether a new bullseye install is better done with the
> > > testing installer at this time, or by first installing buster and
> > > then upgrading?
> > 
> > In general, you are better off installing new rather than upgrading.
> > Installing new means less Buster cruft on your system compared to
> > upgrading buster. Upgrading is a PITA. Why install and then upgrade
> > when installing will get you what you want?
> 
> Thanks, great to know -- but just for the record that didn't use to be 
> the advice -- I'm sure a search through the archives of this list will 
> show times when people advised that the way to install testing was to 
> install stable and then upgrade.

Well, it does seem reasonable that every time a new release comes
out, advice will revert to "use the stable installer and upgrade".
To be fair, people's old advice remains on the archives for ever,
whether or not it's appropriate for the present time.

> That sounded like a faff, for exactly 
> the reasons you mentioned, hence why I asked -- was hoping I'd get the 
> answer you gave!

One might hope that a 3-day-old version of the d-i can make a
reasonable success of installing bullseye. After all, we're now
only a few months out from its release.

Cheers,
David.

Re: Two questions as I prepare for a new install

[Joe]

On Wed, 9 Dec 2020 19:10:53 +
Mark Fletcher  wrote:

> On Mon, Dec 07, 2020 at 06:06:43PM -0700, Charles Curley wrote:
> > On Tue, 8 Dec 2020 00:00:54 +
> > Mark Fletcher  wrote:
> >   
> > > 1. Does anyone have any advice (or a link to offcial advice)
> > > regarding whether a new bullseye install is better done with the
> > > testing installer at this time, or by first installing buster and
> > > then upgrading?  
> > 
> > In general, you are better off installing new rather than upgrading.
> > Installing new means less Buster cruft on your system compared to
> > upgrading buster. Upgrading is a PITA. Why install and then upgrade
> > when installing will get you what you want?
> >   
> 
> Thanks, great to know -- but just for the record that didn't use to
> be the advice -- I'm sure a search through the archives of this list
> will show times when people advised that the way to install testing
> was to install stable and then upgrade. That sounded like a faff, for
> exactly the reasons you mentioned, hence why I asked -- was hoping
> I'd get the answer you gave!

There's a big difference between upgrading a fresh installation of
stable, and one that's a couple of years old and has picked up some
cruft. There's an even bigger difference between upgrading a fresh,
*minimal* installation of stable before adding the desired
applications, and upgrading one packed with applications, any of which
may have issues when upgraded.

I've never had problems upgrading a new, very minimal stable directly to
unstable, something I wouldn't want to do with a well-used, mature
stable. And I have recently upgraded a working netbook from stretch to
buster, which was a sort of trial run to doing it on my server. The test
served its purpose, I won't be upgrading the server.

> 
> Anyone have any thoughts on the second question I asked?
> 

No, currently on AMD and Intel.

-- 
Joe

Re: Two questions as I prepare for a new install

[Mark Fletcher]

On Mon, Dec 07, 2020 at 06:06:43PM -0700, Charles Curley wrote:
> On Tue, 8 Dec 2020 00:00:54 +
> Mark Fletcher  wrote:
> 
> > 1. Does anyone have any advice (or a link to offcial advice)
> > regarding whether a new bullseye install is better done with the
> > testing installer at this time, or by first installing buster and
> > then upgrading?
> 
> In general, you are better off installing new rather than upgrading.
> Installing new means less Buster cruft on your system compared to
> upgrading buster. Upgrading is a PITA. Why install and then upgrade
> when installing will get you what you want?
> 

Thanks, great to know -- but just for the record that didn't use to be 
the advice -- I'm sure a search through the archives of this list will 
show times when people advised that the way to install testing was to 
install stable and then upgrade. That sounded like a faff, for exactly 
the reasons you mentioned, hence why I asked -- was hoping I'd get the 
answer you gave!

Anyone have any thoughts on the second question I asked?

Thanks

Mark

Re: Two questions as I prepare for a new install

[Tixy]

On Tue, 2020-12-08 at 11:48 +0200, Andrei POPESCU wrote:
> On Lu, 07 dec 20, 18:06:43, Charles Curley wrote:
> > On Tue, 8 Dec 2020 00:00:54 +
> > Mark Fletcher  wrote:
> > 
> > > 1. Does anyone have any advice (or a link to offcial advice)
> > > regarding whether a new bullseye install is better done with the
> > > testing installer at this time, or by first installing buster and
> > > then upgrading?
> > 
> > In general, you are better off installing new rather than
> > upgrading.
> > Installing new means less Buster cruft on your system compared to
> > upgrading buster. Upgrading is a PITA. Why install and then upgrade
> > when installing will get you what you want?
> 
> Besides, the installer needs some testing as well ;)
> 
> Anyway, the alpha 3 bullseye installer seems to be in pretty good
> shape.
> 
> https://lists.debian.org/debian-devel-announce/2020/12/msg1.html

That's what I plan on using when my xmas present to myself arrives :-)

-- 
Tixy

Re: Two questions as I prepare for a new install

[Andrei POPESCU]

On Lu, 07 dec 20, 18:06:43, Charles Curley wrote:
> On Tue, 8 Dec 2020 00:00:54 +
> Mark Fletcher  wrote:
> 
> > 1. Does anyone have any advice (or a link to offcial advice)
> > regarding whether a new bullseye install is better done with the
> > testing installer at this time, or by first installing buster and
> > then upgrading?
> 
> In general, you are better off installing new rather than upgrading.
> Installing new means less Buster cruft on your system compared to
> upgrading buster. Upgrading is a PITA. Why install and then upgrade
> when installing will get you what you want?

Besides, the installer needs some testing as well ;)

Anyway, the alpha 3 bullseye installer seems to be in pretty good shape.

https://lists.debian.org/debian-devel-announce/2020/12/msg1.html

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Two questions as I prepare for a new install

[Charles Curley]

On Tue, 8 Dec 2020 00:00:54 +
Mark Fletcher  wrote:

> 1. Does anyone have any advice (or a link to offcial advice)
> regarding whether a new bullseye install is better done with the
> testing installer at this time, or by first installing buster and
> then upgrading?

In general, you are better off installing new rather than upgrading.
Installing new means less Buster cruft on your system compared to
upgrading buster. Upgrading is a PITA. Why install and then upgrade
when installing will get you what you want?

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Two questions as I prepare for a new install

[Mark Fletcher]

Hello list

I am currently amassing the hardware for a new PC build as a Christmas 
present to myself, and plan to install Bullseye on it when the hardware 
is all here.

My current system runs Buster and I thought it would be interesting to 
see what's coming.

I have two questions:

1. Does anyone have any advice (or a link to offcial advice) regarding 
whether a new bullseye install is better done with the testing installer 
at this time, or by first installing buster and then upgrading?

2. My new graphics card is a ASUS-branded nVidia GeForce RTX-2060, which 
means I get to move back to the core non-legacy nVidia driver instead of 
the legacy-legacy one I have been forced to use for some years on my old 
system due to the hardware being 11 years old. Yay... EXCEPT I have read 
hints there is a problem with the up-to-date nVidia driver and recent 
kernels. Does that affect Bullseye? Are there caveats or workarounds I 
should be aware of?

Either direct answers or links to places that answer these would be 
appreciated -- I've been a bit out of the loop recently and suspect I've 
missed a few developments.

Thanks

Mark

Re: Debian 10.4 blank screen After new install

[David Wright]

On Tue 21 Jul 2020 at 22:25:57 (-0500), Edward M Kent wrote:
> Hello All,   I am an old Nube trying to get set up to use a Beaglebone on
> some projects.  I thought I had a successful install after a list of tasks
> was displayed down the screen's left hand edge.

Those "tasks" are the bootable systems being displayed by Grub.

> The list went blank and
> left a - in the upper left corner.

After a 5 second (default) delay, unless you have struck a key, the
system boots the first system in the list.

> This curser soon disappeared leaving a
> blank screen.  The mouse cursed did show up but was a bit erratic.

If the drive is "spinning rust", you should've heard it chattering as
the OS is loaded. It sounds as if the video mode is unsatisfactory.

> I
> rebooted several times and ended back at the same place.

If you press a key during the first 5 seconds, the countdown should
stop. Some suggestions to try:

c   gives you a grub> prompt.
e   should show the contents of the menu for this line in the list.

You can move up and down the list with the arrows. It's even possible
that there are entires for Windows lower down the list.

> This is on a win10 Dell and I can not get back to win10 because I did not
> get the dual boot setup.

I'm hesitant to give you specific Grub commands off the cuff, but if
you type e at the first item in the list, you can experiment with
video modes that might work. Any changes you make in this way
only apply to this boot, so it's a safe way to experiment.

A suggestion I have seen made here in the past is to remove the line:
load_video

Another suggestion, that might be completely useless, is to add the word
  nomodeset
to the end of the line that says something like:
  linux /boot/vmlinuz… …

Others here might have better suggestions.

Cheers,
David.

Debian 10.4 blank screen After new install

[echo test]

Hello,

That blank screen means your hardware has not found the way to load your
boot partition. Verify your BIOS configuration. Try toggling between UEFI
and MBR assuming your bootable device is ok.



Le mer. 22 juil. 2020 à 05:20, Edward M Kent  a écrit :

> Hello All,   I am an old Nube trying to get set up to use a Beaglebone on
> some projects.  I thought I had a successful install after a list of tasks
> was displayed down the screen's left hand edge.  The list went blank and
> left a - in the upper left corner.  This curser soon disappeared leaving a
> blank screen.  The mouse cursed did show up but was a bit erratic.  I
> rebooted several times and ended back at the same place.
> This is on a win10 Dell and I can not get back to win10 because I did not
> get the dual boot setup.
> Thanks for any advice.
> Mick
>
>

Re: Debian 10.4 blank screen After new install

[Umarzuki Mochlis]

Glad to hear it!

On Wed, 22 Jul 2020 at 12:57, Edward M Kent  wrote:
>
> Thanks Umarzuki,  I will take your advice and make a bootable repair disk 
> tomorrow. Too late tonight.  I used f10 on reboot and now have win10.
> Mick
>
>
> On Tue, Jul 21, 2020, 10:33 PM Umarzuki Mochlis  wrote:
>>
>> On Wed, 22 Jul 2020 at 11:21, Edward M Kent  wrote:
>> >
>> > Hello All,   I am an old Nube trying to get set up to use a Beaglebone on 
>> > some projects.  I thought I had a successful install after a list of tasks 
>> > was displayed down the screen's left hand edge.  The list went blank and 
>> > left a - in the upper left corner.  This curser soon disappeared leaving a 
>> > blank screen.  The mouse cursed did show up but was a bit erratic.  I 
>> > rebooted several times and ended back at the same place.
>> > This is on a win10 Dell and I can not get back to win10 because I did not 
>> > get the dual boot setup.
>> > Thanks for any advice.
>> > Mick
>> >
>>
>> Hi,
>>
>> Try Boot-Repair.

Re: Debian 10.4 blank screen After new install

[Edward M Kent]

Thanks Umarzuki,  I will take your advice and make a bootable repair disk
tomorrow. Too late tonight.  I used f10 on reboot and now have win10.
Mick


On Tue, Jul 21, 2020, 10:33 PM Umarzuki Mochlis  wrote:

> On Wed, 22 Jul 2020 at 11:21, Edward M Kent  wrote:
> >
> > Hello All,   I am an old Nube trying to get set up to use a Beaglebone
> on some projects.  I thought I had a successful install after a list of
> tasks was displayed down the screen's left hand edge.  The list went blank
> and left a - in the upper left corner.  This curser soon disappeared
> leaving a blank screen.  The mouse cursed did show up but was a bit
> erratic.  I rebooted several times and ended back at the same place.
> > This is on a win10 Dell and I can not get back to win10 because I did
> not get the dual boot setup.
> > Thanks for any advice.
> > Mick
> >
>
> Hi,
>
> Try Boot-Repair.
>

Re: Debian 10.4 blank screen After new install

[Umarzuki Mochlis]

On Wed, 22 Jul 2020 at 11:21, Edward M Kent  wrote:
>
> Hello All,   I am an old Nube trying to get set up to use a Beaglebone on 
> some projects.  I thought I had a successful install after a list of tasks 
> was displayed down the screen's left hand edge.  The list went blank and left 
> a - in the upper left corner.  This curser soon disappeared leaving a blank 
> screen.  The mouse cursed did show up but was a bit erratic.  I rebooted 
> several times and ended back at the same place.
> This is on a win10 Dell and I can not get back to win10 because I did not get 
> the dual boot setup.
> Thanks for any advice.
> Mick
>

Hi,

Try Boot-Repair.

Debian 10.4 blank screen After new install

[Edward M Kent]

Hello All,   I am an old Nube trying to get set up to use a Beaglebone on
some projects.  I thought I had a successful install after a list of tasks
was displayed down the screen's left hand edge.  The list went blank and
left a - in the upper left corner.  This curser soon disappeared leaving a
blank screen.  The mouse cursed did show up but was a bit erratic.  I
rebooted several times and ended back at the same place.
This is on a win10 Dell and I can not get back to win10 because I did not
get the dual boot setup.
Thanks for any advice.
Mick

Re: New Install Boots to Grub

[Pascal Hambourg]

Le 16/12/2019 à 16:55, Dr. Jason Amerson a écrit :

Hello,

I installed Debian 10.2.0 from a USB drive and the installation finished 
without errors. The only thing that happened during install is that it was 
unable to setup the network. Anyways, I removed the USB drive and rebooted the 
computer. It then booted into grub.


This is expected, as GRUB is Debian's default boot loader.


There was a message telling me I can press TAB to get a list of commands


This is less expected. GRUB should display a menu.
What was the GRUB prompt, simply "grub>" or "grub rescue>" ?
If "grub>", the config file grub.cfg is missing.
If "grub rescue>", GRUB was not installed properly.


but I know nothing about grub and I do not know how to fix the computer so that 
it boots into Debian. Will someone please help me with this?


If you don't know GRUB shell's syntax, then I guess the easier way is to 
boot the Debian installer, select "rescue", follow the steps and 
reinstall GRUB when the option is offered. Make sure you select the 
proper root/boot partition.

Re: New Install Boots to Grub

[Kent West]

On Mon, Dec 16, 2019 at 9:56 AM Dr. Jason Amerson 
wrote:

> Hello,
>
> I installed Debian 10.2.0 from a USB drive and the installation finished
> without errors. The only thing that happened during install is that it was
> unable to setup the network. Anyways, I removed the USB drive and rebooted
> the computer. It then booted into grub. There was a message telling me I
> can press TAB to get a list of commands but I know nothing about grub and I
> do not know how to fix the computer so that it boots into Debian. Will
> someone please help me with this?
>
> Thank you,
>
> Jason
>

Grub should have given you a menu with (probably) two options; something
like:

Debian GNU/Linux
Advanced Options

If you did not get such a menu, something went wrong during the install.

-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

New Install Boots to Grub

[Dr. Jason Amerson]

Hello,

I installed Debian 10.2.0 from a USB drive and the installation finished 
without errors. The only thing that happened during install is that it was 
unable to setup the network. Anyways, I removed the USB drive and rebooted the 
computer. It then booted into grub. There was a message telling me I can press 
TAB to get a list of commands but I know nothing about grub and I do not know 
how to fix the computer so that it boots into Debian. Will someone please help 
me with this?


Thank you,

Jason

Re: New install of buster, worked fine with regular monitor, garbled display but with good mouse pointer when connected to AV setup

[Phil Reynolds]

On Mon, 12 Aug 2019 15:26:49 +0100
Phil Reynolds  wrote:

> I recently installed buster on a machine so that I could install kodi
> on it for the purpose of playing Internet content on my lounge AV
> setup. It all worked fine with a regular monitor.
> 
> On trying to get it connected to the AV setup today, I get a rather
> strange problem. All text mode display is absolutely fine, but when
> gdm3 starts, I see a good mouse pointer, but all other graphical
> output is "torn up", in a way similar to the effect you would see on
> an old TV if the horizontal hold is badly out of adjustment. You can
> see my actual display here: https://imgur.com/a/0Vob8Na
> 
> I would show you my Xorg log but there isn't one. At present I have
> only virtual console access to the machine. So, my question is, how
> can I resolve this problem?

This matter has been resolved... it turned out to be a wayland problem.
On disabling wayland in /etc/gdm3/daemon.conf, a correct display
appears on the AV setup.

-- 
Phil Reynolds
mail: phil-deb...@tinsleyviaduct.com
Web: http://phil.tinsleyviaduct.com/

New install of buster, worked fine with regular monitor, garbled display but with good mouse pointer when connected to AV setup

[Phil Reynolds]

I recently installed buster on a machine so that I could install kodi
on it for the purpose of playing Internet content on my lounge AV
setup. It all worked fine with a regular monitor.

On trying to get it connected to the AV setup today, I get a rather
strange problem. All text mode display is absolutely fine, but when gdm3
starts, I see a good mouse pointer, but all other graphical output is
"torn up", in a way similar to the effect you would see on an old TV if
the horizontal hold is badly out of adjustment. You can see my actual
display here: https://imgur.com/a/0Vob8Na

I would show you my Xorg log but there isn't one. At present I have
only virtual console access to the machine. So, my question is, how can
I resolve this problem?

-- 
Phil Reynolds
mail: phil-deb...@tinsleyviaduct.com
Web: http://phil.tinsleyviaduct.com/

Re: trouble by new install of claws mail

[Andreas Ronnquist]

On Thu, 13 Sep 2018 23:50:04 +0200,
arne wrote:

>The message:
>
>"Your Claws Mail configuration is from a newer version than the version
>which you are currently using."
>
>Claws Mail is right.
>
>I did copy Claws settings from debian testing to a new system on
>stable.
>
>I do not want to loose my settings.
>
>Claws seems to work OK but the message remains.
>
>Any ideas on  how to solve this?
>
>And no, I do not want to switch to testing again.
>
>Thanks!
>

See my previous answer, it is described in more detail at

https://www.claws-mail.org/cvc.php

and see the details under "Manual downgrading to the previous version".

-- Andreas Rönnquist
mailingli...@gusnan.se
andr...@ronnquist.net

Re: trouble by new install of claws mail

[Andreas Ronnquist]

On Thu, 13 Sep 2018 23:50:04 +0200,
arne wrote:

>The message:
>
>"Your Claws Mail configuration is from a newer version than the version
>which you are currently using."
>
>Claws Mail is right.
>
>I did copy Claws settings from debian testing to a new system on
>stable.
>
>I do not want to loose my settings.
>
>Claws seems to work OK but the message remains.
>
>Any ideas on  how to solve this?
>

Edit 

$(HOME)/.claws-mail/accountrc

and change every line containing "config_version" from 3 (which it is in
the version from testing) to 2 - once for each account you have.

I have done this recently, and didn't notice any regressions.

Also, notice that claws-mail 3.17.1 is available from backports.

-- Andreas Rönnquist
mailingli...@gusnan.se
andr...@ronnquist.net

trouble by new install of claws mail

[arne]

The message:

"Your Claws Mail configuration is from a newer version than the version
which you are currently using."

Claws Mail is right.

I did copy Claws settings from debian testing to a new system on stable.

I do not want to loose my settings.

Claws seems to work OK but the message remains.

Any ideas on  how to solve this?

And no, I do not want to switch to testing again.

Thanks!

Re: new install of amd64, 9-4 from iso #1

[Gene Heskett]

On Friday 15 June 2018 02:28:35 David Christensen wrote:

> On 06/14/18 01:52, Gene Heskett wrote:
> > I'm seeing, at newegg et all, what is said to be a 3d nand that
> > seems to be the higher capacity drive, 240 GB etc, for prices in the
> > $90 range. But you are mentioning PCIe. Is SATA about to be
> > replaced, and I'll have to locate yet another motherboard to keep up
> > with the Jones's?
>
> I expect motherboards and drives with SATA interfaces will be around
> for many more years -- the interface is ubiquitous and fast/ cheap
> enough.
>
>
> I would consider the PCIe stuff for newer machines and/or machines
> running services or applications that need the performance.
>
> > On the hot swap cage front, the center pocket, even with a new
> > cable, a cast iron bitch to install, is still not at all happy with
> > the 2T drive I've installed 9.4 on, spamming my logs with resets.
> > Move the drive to the last sata socket, hanging out of the side of
> > the case, and its happy as a clam. Cheap cables, $6.50 for ten of
> > them, but they claim 6GB/sec, so I'll try yet another cable today
> > when I have both eyes open at the same time.
>
> Bad SATA cables and/or connectors are a common problem.  I now mark
> every SATA cable with a serial number and track them, to help with
> trouble-shooting.
>
>
> Using drive trays/ bays adds another level of hardware that can cause
> problems.  The only advice I can offer is to take meticulous notes and
> have spare parts for A-B testing.
>
> > I've also been battling a sudden loss of sound, took my speakers
> > apart and replaced 6 open electrolytic caps in the amp, (I am a
> > C.E.T. and have all the test gear and tools for that), didn't help,
> > went out to wally's and bought a twin of it, then found the green
> > led for the front channel was dark in kmix. But this set has lots
> > more distortion, so now that I know the machine is outputting sound
> > I'll retry the repaired kit again.
>
> For sound on Linux, I use Intel desktop boards, Debian stable, and
> cross my fingers.  It usually just works.  Whenever I try to add audio
> stuff, sound usually breaks to some lesser or greater extent.
>

Which sounds a lot better, so wallies new one went back last night for a 
refund. Since they were identical, I suspect they were both made in the 
same week 3 or 4 years ago and the capacitors have died sitting on the 
shelf. There were 6 caps, smaller stuff .22 uf to 20uf that measured in 
the 30 pf range. All got replaced with 50 to 100 uf stuff. Much more 
dependable than the teeny stuff they bought out of a sale wagon in front 
a a parts house in shangzui.

> David



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: new install of amd64, 9-4 from iso #1

[David Christensen]

On 06/14/18 01:52, Gene Heskett wrote:

I'm seeing, at newegg et all, what is said to be a 3d nand that seems to
be the higher capacity drive, 240 GB etc, for prices in the $90 range.
But you are mentioning PCIe. Is SATA about to be replaced, and I'll have
to locate yet another motherboard to keep up with the Jones's?


I expect motherboards and drives with SATA interfaces will be around for 
many more years -- the interface is ubiquitous and fast/ cheap enough.



I would consider the PCIe stuff for newer machines and/or machines 
running services or applications that need the performance.




On the hot swap cage front, the center pocket, even with a new cable, a
cast iron bitch to install, is still not at all happy with the 2T drive
I've installed 9.4 on, spamming my logs with resets. Move the drive to
the last sata socket, hanging out of the side of the case, and its happy
as a clam. Cheap cables, $6.50 for ten of them, but they claim 6GB/sec,
so I'll try yet another cable today when I have both eyes open at the
same time.


Bad SATA cables and/or connectors are a common problem.  I now mark 
every SATA cable with a serial number and track them, to help with 
trouble-shooting.



Using drive trays/ bays adds another level of hardware that can cause 
problems.  The only advice I can offer is to take meticulous notes and 
have spare parts for A-B testing.




I've also been battling a sudden loss of sound, took my speakers apart
and replaced 6 open electrolytic caps in the amp, (I am a C.E.T. and
have all the test gear and tools for that), didn't help, went out to
wally's and bought a twin of it, then found the green led for the front
channel was dark in kmix. But this set has lots more distortion, so now
that I know the machine is outputting sound I'll retry the repaired kit
again.


For sound on Linux, I use Intel desktop boards, Debian stable, and cross 
my fingers.  It usually just works.  Whenever I try to add audio stuff, 
sound usually breaks to some lesser or greater extent.



David

Re: new install of amd64, 9-4 from iso #1

[Gene Heskett]

On Thursday 14 June 2018 05:00:34 Jimmy Johnson wrote:

> On 06/11/2018 04:42 AM, Gene Heskett wrote:
> > On Monday 11 June 2018 06:40:41 Mirko Parthey wrote:
> >> On Sun, Jun 10, 2018 at 04:44:16PM -0400, Gene Heskett wrote:
> >>> and 3: to  treat the grub install as if there are no other drives
> >>> hooked up. I don't need grub to fill half the boot screen with
> >>> data from the other drives.
> >>
> >> Once your Debian installation is finished, put this in
> >> /etc/default/grub: GRUB_DISABLE_OS_PROBER=true
> >>
> >> Then run
> >>update-grub
> >> to remove the unwanted entries from your grub menu.
> >>
> >> The Grub info documentation describes it as follows:
> >> 'GRUB_DISABLE_OS_PROBER'
> >>   Normally, 'grub-mkconfig' will try to use the external
> >> 'os-prober' program, if installed, to discover other operating
> >> systems installed on the same system and generate appropriate menu
> >> entries for them.  Set this option to 'true' to disable this.
> >>
> >> Disconnecting disks while installing Debian can help avoid
> >> mistakes. However, it does not permanently suppress the boot menu
> >> entries referring to other OS installations.
> >>
> >> Regards,
> >> Mirko
> >
> > Thanks Mirko, that will be handy.
>
> #3 problem, have you looked to see if you can remove drives in your
> BIOS, if you can you won't need to crack your case.
>
The sides have been off this huge tower for a decade. Easier to do a 
dusting and cleaning, and helps with the heat trapping. So "cracking the 
case" isn't a big deal, its already cracked wide open.
> Cheers,



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: new install of amd64, 9-4 from iso #1

[Jimmy Johnson]

On 06/11/2018 04:42 AM, Gene Heskett wrote:

On Monday 11 June 2018 06:40:41 Mirko Parthey wrote:


On Sun, Jun 10, 2018 at 04:44:16PM -0400, Gene Heskett wrote:

and 3: to  treat the grub install as if there are no other drives
hooked up. I don't need grub to fill half the boot screen with data
from the other drives.


Once your Debian installation is finished, put this in
/etc/default/grub: GRUB_DISABLE_OS_PROBER=true

Then run
   update-grub
to remove the unwanted entries from your grub menu.

The Grub info documentation describes it as follows:
'GRUB_DISABLE_OS_PROBER'
  Normally, 'grub-mkconfig' will try to use the external
'os-prober' program, if installed, to discover other operating systems
installed on the same system and generate appropriate menu entries for
them.  Set this option to 'true' to disable this.

Disconnecting disks while installing Debian can help avoid mistakes.
However, it does not permanently suppress the boot menu entries
referring to other OS installations.

Regards,
Mirko


Thanks Mirko, that will be handy.



#3 problem, have you looked to see if you can remove drives in your 
BIOS, if you can you won't need to crack your case.


Cheers,
--
Jimmy Johnson

Devuan Jessie - TDE Trinity R14.0.4 - AMD A8-7600 - EXT4 at sda2
Registered Linux User #380263

Re: new install of amd64, 9-4 from iso #1

[Gene Heskett]

On Thursday 14 June 2018 01:03:12 David Christensen wrote:

> On 06/10/18 21:35, Gene Heskett wrote:
> > On Monday 11 June 2018 00:16:39 David Christensen wrote:
> >> On 06/10/18 13:44, Gene Heskett wrote:
> >>> Greetings all;
> >>>
> >>> I have the dvd written, and a new 2T drive currently occupying the
> >>> /dev/sdc slot.
> >>>
> >>> What I want, since the drive has been partitioned to /boot, /home,
> >>> /, and swap, is 1; for this install to not touch any other drive
> >>> currently mounted, and 2; use the partitions I've already setup on
> >>> this new drive without arguing with me.
> >>>
> >>> and 3: to  treat the grub install as if there are no other drives
> >>> hooked up. I don't need grub to fill half the boot screen with
> >>> data from the other drives.
> >>>
> >>> How do I best achieve that?
> >>
> >> Disconnect all drives except the new 2 TB drive and your optical
> >> drive, then boot the installer.  That should solve all three of
> >> your requirements.
>
> I thought about that some more, and the GRUB part could get messy if
> you reconnect additional drives with bootable partitions and do a
> kernel, etc., upgrade that runs GRUB.  I avoid that problem by having
> only one system drive installed at a a time.
>
> >> I put mobile racks in all my desktop and server cases, and use
> >> small (16~80 GB) HDD's/SSD's for boot, swap, and root.  When I want
> >> a different OS, I power down, swap system drives, and boot.
> >>
> >>
> >> (I keep the local contents of my home directory minimal, put the
> >> majority of my data into a personal share on my file server, and
> >> mount that into my home directory.)
> >
> > I can see I need to watch the sales for a good price on 60 to 100
> > gig SSD's. Is there a longer lasting version coming down the line
> > that I should be aware of?
>
> I starting buying Intel 520 Series SSD's several years ago.  They are
> well matched to my Intel DQ67SWR/ Intel Core i7-2600S machine
> (benchmark over 500 MB/s, depending).  The last time I checked them
> with the Intel SSD Toolbox, they showed very little wear (99%+ life
> available?).
>
>
> For my older P4 machines, I bought used SAMSUNG SSD UM410 Series 2.5"
> 16GB drives for $10~15 each.  eBay doesn't seem to have that exact
> model now, but there are other 16 GB SSD's to choose from.
>
>
> I think most any respectable SSD deployed as a Linux system drive is
> going to outlast the computer it is installed in.
>
>
> I bought a 2015 MacBook Pro a few months back.  I has a 256 GB SSD
> with an Apple-proprietary four-lane PCIe 3.0 interface (8.0 GT/s, 31.5
> Gbit/s).  Very impressive performance.  The PC equivalent would seem
> to be a motherboard and drive with a NVMe PCIe M.2 interface or with a
> PCIe 3.0 4x, 8x, or 16x interface.
>
>
> PCIe 3D XPoint drives (Intel Optane) seem to be the current king of
> the mountain.
>
I'm seeing, at newegg et all, what is said to be a 3d nand that seems to 
be the higher capacity drive, 240 GB etc, for prices in the $90 range. 
But you are mentioning PCIe. Is SATA about to be replaced, and I'll have 
to locate yet another motherboard to keep up with the Jones's?

On the hot swap cage front, the center pocket, even with a new cable, a 
cast iron bitch to install, is still not at all happy with the 2T drive 
I've installed 9.4 on, spamming my logs with resets. Move the drive to 
the last sata socket, hanging out of the side of the case, and its happy 
as a clam. Cheap cables, $6.50 for ten of them, but they claim 6GB/sec, 
so I'll try yet another cable today when I have both eyes open at the 
same time.

I've also been battling a sudden loss of sound, took my speakers apart 
and replaced 6 open electrolytic caps in the amp, (I am a C.E.T. and 
have all the test gear and tools for that), didn't help, went out to 
wally's and bought a twin of it, then found the green led for the front 
channel was dark in kmix. But this set has lots more distortion, so now 
that I know the machine is outputting sound I'll retry the repaired kit 
again.

> David

Thanks David.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: new install of amd64, 9-4 from iso #1

[David Christensen]

On 06/10/18 21:35, Gene Heskett wrote:

On Monday 11 June 2018 00:16:39 David Christensen wrote:


On 06/10/18 13:44, Gene Heskett wrote:

Greetings all;

I have the dvd written, and a new 2T drive currently occupying the
/dev/sdc slot.

What I want, since the drive has been partitioned to /boot, /home,
/, and swap, is 1; for this install to not touch any other drive
currently mounted, and 2; use the partitions I've already setup on
this new drive without arguing with me.

and 3: to  treat the grub install as if there are no other drives
hooked up. I don't need grub to fill half the boot screen with data
from the other drives.

How do I best achieve that?


Disconnect all drives except the new 2 TB drive and your optical
drive, then boot the installer.  That should solve all three of your
requirements.


I thought about that some more, and the GRUB part could get messy if you 
reconnect additional drives with bootable partitions and do a kernel, 
etc., upgrade that runs GRUB.  I avoid that problem by having only one 
system drive installed at a a time.




I put mobile racks in all my desktop and server cases, and use small
(16~80 GB) HDD's/SSD's for boot, swap, and root.  When I want a
different OS, I power down, swap system drives, and boot.


(I keep the local contents of my home directory minimal, put the
majority of my data into a personal share on my file server, and mount
that into my home directory.)


I can see I need to watch the sales for a good price on 60 to 100 gig
SSD's. Is there a longer lasting version coming down the line that I
should be aware of?


I starting buying Intel 520 Series SSD's several years ago.  They are 
well matched to my Intel DQ67SWR/ Intel Core i7-2600S machine (benchmark 
over 500 MB/s, depending).  The last time I checked them with the Intel 
SSD Toolbox, they showed very little wear (99%+ life available?).



For my older P4 machines, I bought used SAMSUNG SSD UM410 Series 2.5" 
16GB drives for $10~15 each.  eBay doesn't seem to have that exact model 
now, but there are other 16 GB SSD's to choose from.



I think most any respectable SSD deployed as a Linux system drive is 
going to outlast the computer it is installed in.



I bought a 2015 MacBook Pro a few months back.  I has a 256 GB SSD with 
an Apple-proprietary four-lane PCIe 3.0 interface (8.0 GT/s, 31.5 
Gbit/s).  Very impressive performance.  The PC equivalent would seem to 
be a motherboard and drive with a NVMe PCIe M.2 interface or with a PCIe 
3.0 4x, 8x, or 16x interface.



PCIe 3D XPoint drives (Intel Optane) seem to be the current king of the 
mountain.



David

Re: new install of amd64, 9-4 from iso #1

[Gene Heskett]

On Monday 11 June 2018 06:40:41 Mirko Parthey wrote:

> On Sun, Jun 10, 2018 at 04:44:16PM -0400, Gene Heskett wrote:
> > and 3: to  treat the grub install as if there are no other drives
> > hooked up. I don't need grub to fill half the boot screen with data
> > from the other drives.
>
> Once your Debian installation is finished, put this in
> /etc/default/grub: GRUB_DISABLE_OS_PROBER=true
>
> Then run
>   update-grub
> to remove the unwanted entries from your grub menu.
>
> The Grub info documentation describes it as follows:
> 'GRUB_DISABLE_OS_PROBER'
>  Normally, 'grub-mkconfig' will try to use the external
> 'os-prober' program, if installed, to discover other operating systems
> installed on the same system and generate appropriate menu entries for
> them.  Set this option to 'true' to disable this.
>
> Disconnecting disks while installing Debian can help avoid mistakes.
> However, it does not permanently suppress the boot menu entries
> referring to other OS installations.
>
> Regards,
> Mirko

Thanks Mirko, that will be handy.


-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: new install of amd64, 9-4 from iso #1

[Mirko Parthey]

On Sun, Jun 10, 2018 at 04:44:16PM -0400, Gene Heskett wrote:
> and 3: to  treat the grub install as if there are no other drives hooked 
> up. I don't need grub to fill half the boot screen with data from the 
> other drives.

Once your Debian installation is finished, put this in /etc/default/grub:
GRUB_DISABLE_OS_PROBER=true

Then run
  update-grub
to remove the unwanted entries from your grub menu.

The Grub info documentation describes it as follows:
'GRUB_DISABLE_OS_PROBER'
 Normally, 'grub-mkconfig' will try to use the external 'os-prober'
 program, if installed, to discover other operating systems
 installed on the same system and generate appropriate menu entries
 for them.  Set this option to 'true' to disable this.

Disconnecting disks while installing Debian can help avoid mistakes.
However, it does not permanently suppress the boot menu entries referring to
other OS installations.

Regards,
Mirko

Re: new install of amd64, 9-4 from iso #1

[Gene Heskett]

On Monday 11 June 2018 00:16:39 David Christensen wrote:

> On 06/10/18 13:44, Gene Heskett wrote:
> > Greetings all;
> >
> > I have the dvd written, and a new 2T drive currently occupying the
> > /dev/sdc slot.
> >
> > What I want, since the drive has been partitioned to /boot, /home,
> > /, and swap, is 1; for this install to not touch any other drive
> > currently mounted, and 2; use the partitions I've already setup on
> > this new drive without arguing with me.
> >
> > and 3: to  treat the grub install as if there are no other drives
> > hooked up. I don't need grub to fill half the boot screen with data
> > from the other drives.
> >
> > How do I best achieve that?
>
> On 06/10/18 20:41, Rick Thomas wrote:
> > As others have pointed out, 1 and 2 are just a matter of using the
> > tools the installer provides.  To accomplish 2, you should probably
> > choose “manual” partitioning.  You may need to choose “expert” mode
> > at boot time for the installer.
> >
> > As for 3, my approach would be to open up the box and temporarily
> > disconnect the power from the other two disks while installing to
> > the third disk.
>
> If you want to disconnect a drive:  disconnect both the power and the
> data cables, so that the data cable cannot back feed the drive
> electronics.
>
>
> Disconnect all drives except the new 2 TB drive and your optical
> drive, then boot the installer.  That should solve all three of your
> requirements.  Once you've booted into your fresh OS, edit
> /etc/crypttab and/or /etc/fstab to use UUID's or /dev/disk/* paths to
> uniquely identify the partitions.  (I use MBR partitioning for my
> system drives, and swap partitions appear to lack a UUID.  /dev/disk/*
> paths seem to work for swap partitions on recent Debian
> distributions.)
>
>
> You will want to choose "manual" partitioning in the installer to
> select the partitions/ swap spaces/ file systems you have already
> created.
>
>
> I don't think "expert" mode is required -- it just seems to make the
> installer steps explicit (?).
>
> > After the install you can reconnect the power and
> > you will wind up with two bootable drives. You will then have to
> > choose between them at the BIOS level.
>
> I put mobile racks in all my desktop and server cases, and use small
> (16~80 GB) HDD's/SSD's for boot, swap, and root.  When I want a
> different OS, I power down, swap system drives, and boot.
>
>
> (I keep the local contents of my home directory minimal, put the
> majority of my data into a personal share on my file server, and mount
> that into my home directory.)
>
I can see I need to watch the sales for a good price on 60 to 100 gig 
SSD's. Is there a longer lasting version coming down the line that I 
should be aware of?
>
> David



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: new install of amd64, 9-4 from iso #1

[Gene Heskett]

On Sunday 10 June 2018 23:41:36 Rick Thomas wrote:

> > On Jun 10, 2018, at 1:44 PM, Gene Heskett 
> > wrote:
> >
> > Greetings all;
> >
> > I have the dvd written, and a new 2T drive currently occupying
> > the /dev/sdc slot.
> >
> > What I want, since the drive has been partitioned to /boot, /home,
> > /, and swap, is 1; for this install to not touch any other drive
> > currently mounted, and 2; use the partitions I've already setup on
> > this new drive without arguing with me.
> >
> > and 3: to  treat the grub install as if there are no other drives
> > hooked up. I don't need grub to fill half the boot screen with data
> > from the other drives.
> >
> > How do I best achieve that?
>
> As others have pointed out, 1 and 2 are just a matter of using the
> tools the installer provides.  To accomplish 2, you should probably
> choose “manual” partitioning.  You may need to choose “expert” mode at
> boot time for the installer.
>
> As for 3, my approach would be to open up the box and temporarily
> disconnect the power from the other two disks while installing to the
> third disk.  After the install you can reconnect the power and you
> will wind up with two bootable drives. You will then have to choose
> between them at the BIOS level.

This is made easy because 3 of the drives are in a 3 drive hot swap cage, 
so I can just open the doors and eject them 1/2 an inch. The drive its 
to be installed on is hanging out of the side of the machine.
>
> Hope that helps!
> Rick

Yes, its helpfull Rick, might keep me from shooting myself in the foot. 
Thanks.


-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: new install of amd64, 9-4 from iso #1

[Gene Heskett]

On Sunday 10 June 2018 20:55:11 Charlie S wrote:

> On Sun, 10 Jun 2018 16:44:16 -0400 Gene Heskett sent:
> > Greetings all;
> >
> > I have the dvd written, and a new 2T drive currently occupying
> > the /dev/sdc slot.
> >
> > What I want, since the drive has been partitioned to /boot, /home,
> > /, and swap, is 1; for this install to not touch any other drive
> > currently mounted, and 2; use the partitions I've already setup on
> > this new drive without arguing with me.
> >
> > and 3: to  treat the grub install as if there are no other drives
> > hooked up. I don't need grub to fill half the boot screen with data
> > from the other drives.
> >
> > How do I best achieve that?
>
>   After contemplation, my reply is:
>
>   The installer will allow you to bypass any partitions you don't
>   wish to acknowledge or touch. The others it will use if so
>   instructed for the purposes you specify.
>
> If it was me, though it might not be required, /boot, /home, /, and
> swap, you have created would be formatted by the installer. Just to be
> sure to be sure. I do it this way, but as stated, probably not
> required.
>
> I'm unsure about the GRUB controls and just how much it shows without
> actually asking it to show these? It has been a long time since I put
> anything but one Debian operating system on a disk. Also probably in
> ways that are not necessarily correct or required.


If the resultant disk is 100% self-contained, I can then add the others 
in fstab to be /media/wheezy_this /media/wheezy_that later when I'm 
recovering my kmail database. That won't be until I've installed TDE.
That will be the 2nd operation, first will be to get networking working. 
3rd will be to copy wheezy/home/amanda, become amanda and build/install 
it so I have a working backup.

> Sorry I can't help you more.
> Charlie

Thanks Charlie.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: new install of amd64, 9-4 from iso #1

[David Christensen]

On 06/10/18 13:44, Gene Heskett wrote:

Greetings all;

I have the dvd written, and a new 2T drive currently occupying the 
/dev/sdc slot.


What I want, since the drive has been partitioned to /boot, /home,
/, and swap, is 1; for this install to not touch any other drive 
currently mounted, and 2; use the partitions I've already setup on 
this new drive without arguing with me.


and 3: to  treat the grub install as if there are no other drives 
hooked up. I don't need grub to fill half the boot screen with data 
from the other drives.


How do I best achieve that?



On 06/10/18 20:41, Rick Thomas wrote:
As others have pointed out, 1 and 2 are just a matter of using the 
tools the installer provides.  To accomplish 2, you should probably 
choose “manual” partitioning.  You may need to choose “expert” mode

at boot time for the installer.

As for 3, my approach would be to open up the box and temporarily 
disconnect the power from the other two disks while installing to
the third disk. 


If you want to disconnect a drive:  disconnect both the power and the 
data cables, so that the data cable cannot back feed the drive electronics.



Disconnect all drives except the new 2 TB drive and your optical drive, 
then boot the installer.  That should solve all three of your 
requirements.  Once you've booted into your fresh OS, edit /etc/crypttab 
and/or /etc/fstab to use UUID's or /dev/disk/* paths to uniquely 
identify the partitions.  (I use MBR partitioning for my system drives, 
and swap partitions appear to lack a UUID.  /dev/disk/* paths seem to 
work for swap partitions on recent Debian distributions.)



You will want to choose "manual" partitioning in the installer to select 
the partitions/ swap spaces/ file systems you have already created.



I don't think "expert" mode is required -- it just seems to make the 
installer steps explicit (?).



After the install you can reconnect the power and
you will wind up with two bootable drives. You will then have to
choose between them at the BIOS level.
I put mobile racks in all my desktop and server cases, and use small 
(16~80 GB) HDD's/SSD's for boot, swap, and root.  When I want a 
different OS, I power down, swap system drives, and boot.



(I keep the local contents of my home directory minimal, put the 
majority of my data into a personal share on my file server, and mount 
that into my home directory.)



David

Re: new install of amd64, 9-4 from iso #1

[Gene Heskett]

On Sunday 10 June 2018 20:23:49 Mark Fletcher wrote:

> On Sun, Jun 10, 2018 at 04:44:16PM -0400, Gene Heskett wrote:
> > Greetings all;
> >
> > I have the dvd written, and a new 2T drive currently occupying
> > the /dev/sdc slot.
> >
> > What I want, since the drive has been partitioned to /boot, /home,
> > /, and swap, is 1; for this install to not touch any other drive
> > currently mounted, and 2; use the partitions I've already setup on
> > this new drive without arguing with me.
> >
> > and 3: to  treat the grub install as if there are no other drives
> > hooked up. I don't need grub to fill half the boot screen with data
> > from the other drives.
> >
> > How do I best achieve that?
> >
> > Thanks a bunch.
>
> 1 and 2 are simply a matter of giving the sensible answers to the
> appropriate questions from the installer. I can't remember exactly
> what the options are called but there is an expert partition mode that
> allows you to partition the disk how you want and I'd use that to
> verify the partitions are as you want and not change anything, map the
> parts of the filesystem you want to go on each partition in the
> installer, then continue.
>
> If you don't tell it to install anything to the other disks then it
> won't.
>
> For 3, I think I need to defer to the grub experts, not sure if you
> will have to preseed your install or if there is an easier way.
>
> Mark

Thanks Mark.  Are there any grub guru's about for question #3?

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: new install of amd64, 9-4 from iso #1

[Rick Thomas]

> On Jun 10, 2018, at 1:44 PM, Gene Heskett  wrote:
> 
> Greetings all;
> 
> I have the dvd written, and a new 2T drive currently occupying 
> the /dev/sdc slot.
> 
> What I want, since the drive has been partitioned to /boot, /home, /, and 
> swap, is 1; for this install to not touch any other drive currently 
> mounted, and 2; use the partitions I've already setup on this new drive 
> without arguing with me.
> 
> and 3: to  treat the grub install as if there are no other drives hooked 
> up. I don't need grub to fill half the boot screen with data from the 
> other drives.
> 
> How do I best achieve that?

As others have pointed out, 1 and 2 are just a matter of using the tools the 
installer provides.  To accomplish 2, you should probably choose “manual” 
partitioning.  You may need to choose “expert” mode at boot time for the 
installer.

As for 3, my approach would be to open up the box and temporarily disconnect 
the power from the other two disks while installing to the third disk.  After 
the install you can reconnect the power and you will wind up with two bootable 
drives. You will then have to choose between them at the BIOS level.

Hope that helps!
Rick

Re: new install of amd64, 9-4 from iso #1

[Charlie S]

On Sun, 10 Jun 2018 16:44:16 -0400 Gene Heskett sent:

> Greetings all;
> 
> I have the dvd written, and a new 2T drive currently occupying 
> the /dev/sdc slot.
> 
> What I want, since the drive has been partitioned to /boot, /home, /,
> and swap, is 1; for this install to not touch any other drive
> currently mounted, and 2; use the partitions I've already setup on
> this new drive without arguing with me.
> 
> and 3: to  treat the grub install as if there are no other drives
> hooked up. I don't need grub to fill half the boot screen with data
> from the other drives.
> 
> How do I best achieve that?


After contemplation, my reply is:

The installer will allow you to bypass any partitions you don't
wish to acknowledge or touch. The others it will use if so
instructed for the purposes you specify.

If it was me, though it might not be required, /boot, /home, /, and
swap, you have created would be formatted by the installer. Just to be
sure to be sure. I do it this way, but as stated, probably not required.

I'm unsure about the GRUB controls and just how much it shows without
actually asking it to show these? It has been a long time since I put
anything but one Debian operating system on a disk. Also probably in
ways that are not necessarily correct or required.

Sorry I can't help you more.
Charlie
-- 
Registered Linux User:- 329524
***

Many eyes go through the meadow, but few see the flowers in
it. ...Ralph Waldo Emerson

***

Debian GNU/Linux - Magic indeed.

-

Re: new install of amd64, 9-4 from iso #1

[Mark Fletcher]

On Sun, Jun 10, 2018 at 04:44:16PM -0400, Gene Heskett wrote:
> Greetings all;
> 
> I have the dvd written, and a new 2T drive currently occupying 
> the /dev/sdc slot.
> 
> What I want, since the drive has been partitioned to /boot, /home, /, and 
> swap, is 1; for this install to not touch any other drive currently 
> mounted, and 2; use the partitions I've already setup on this new drive 
> without arguing with me.
> 
> and 3: to  treat the grub install as if there are no other drives hooked 
> up. I don't need grub to fill half the boot screen with data from the 
> other drives.
> 
> How do I best achieve that?
> 
> Thanks a bunch.
> 

1 and 2 are simply a matter of giving the sensible answers to the 
appropriate questions from the installer. I can't remember exactly what 
the options are called but there is an expert partition mode that allows 
you to partition the disk how you want and I'd use that to verify the 
partitions are as you want and not change anything, map the parts of the 
filesystem you want to go on each partition in the installer, then 
continue.

If you don't tell it to install anything to the other disks then it won't.

For 3, I think I need to defer to the grub experts, not sure if you will 
have to preseed your install or if there is an easier way.

Mark

new install of amd64, 9-4 from iso #1

[Gene Heskett]

Greetings all;

I have the dvd written, and a new 2T drive currently occupying 
the /dev/sdc slot.

What I want, since the drive has been partitioned to /boot, /home, /, and 
swap, is 1; for this install to not touch any other drive currently 
mounted, and 2; use the partitions I've already setup on this new drive 
without arguing with me.

and 3: to  treat the grub install as if there are no other drives hooked 
up. I don't need grub to fill half the boot screen with data from the 
other drives.

How do I best achieve that?

Thanks a bunch.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: New install Jesse 8.6.0...grub2 problem

[Lisi Reisz]

On Sunday 30 October 2016 15:47:59 Mark Fletcher wrote:
> On Sun, Oct 30, 2016 at 10:35:59AM -0400, Cindy-Sue Causey wrote:
> > On 10/30/16, Pascal Hambourg  wrote:
> > > Le 30/10/2016 à 13:13, Lisi Reisz a écrit :
> > >> On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:
> > >>> The result of bootinfoscript would be a good starting point.
> > >>
> > >> I have Jessie fully updated and aptitude can't find bootinfoscript.
> > >
> > > How did you search ? It is a command, not a package name. The package
> > > name is boot-info-script (don't ask me why hyphens were inserted).
> >
> > I'm going to step out onto a limb and presume she did what I just did,
> > input "bootinfoscrript" into her preferred Debian package manager and
> > let 'er rip. In fact, Lisi referenced "aptitude", her preferred
> > package manager.
> >
> > For mine, I use "apt-cache search". It returns feedback on anything
> > you input, not just package names. I a-sume aptitude and others
> > perform similarly.
> >
> > When queried via "apt-cache search", "bootinfoscript" received back
> > zero possibilities here, too. However, querying "boot-info-script" did
> > return something. One returned possibility:
> >
> > "boot-info-script - inspect boot environment"
> >
> > Cool. Will be checking it out.
>
> A lot of people seem to forget or not know about apt-file. It allows
> searches in both directions -- apt-file show  will tell
> you what files are installed by the package and where they go. apt-file
> search  shows which package the file came from. The package does
> _not_ need to be installed for apt-file to do its work, but you do need
> to have run apt-file update before expecting up to date and correct
> answers.
>
> Very similar, I think, to apt-cache search when doing apt-file show but
> with the additional ability to go the other way. For example I just did
> apt-file search bootinfoscript to find out that the file is contained in
> boot-info-script.

lisi@Eros:~$ apt-file search bootinfoscript
boot-info-script: /usr/sbin/bootinfoscript
boot-info-script: /usr/share/man/man8/bootinfoscript.8.gz
lisi@Eros:~$ 

\o/ \o/

Thanks, Mark. :-)

Lisi

>
> Mark

Re: New install Jesse 8.6.0...grub2 problem

[Mark Fletcher]

On Sun, Oct 30, 2016 at 10:35:59AM -0400, Cindy-Sue Causey wrote:
> On 10/30/16, Pascal Hambourg  wrote:
> > Le 30/10/2016 à 13:13, Lisi Reisz a écrit :
> >> On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:
> >>>
> >>> The result of bootinfoscript would be a good starting point.
> >>
> >> I have Jessie fully updated and aptitude can't find bootinfoscript.
> >
> > How did you search ? It is a command, not a package name. The package
> > name is boot-info-script (don't ask me why hyphens were inserted).
> 
> 
> I'm going to step out onto a limb and presume she did what I just did,
> input "bootinfoscrript" into her preferred Debian package manager and
> let 'er rip. In fact, Lisi referenced "aptitude", her preferred
> package manager.
> 
> For mine, I use "apt-cache search". It returns feedback on anything
> you input, not just package names. I a-sume aptitude and others
> perform similarly.
> 
> When queried via "apt-cache search", "bootinfoscript" received back
> zero possibilities here, too. However, querying "boot-info-script" did
> return something. One returned possibility:
> 
> "boot-info-script - inspect boot environment"
> 
> Cool. Will be checking it out.
> 

A lot of people seem to forget or not know about apt-file. It allows 
searches in both directions -- apt-file show  will tell 
you what files are installed by the package and where they go. apt-file 
search  shows which package the file came from. The package does 
_not_ need to be installed for apt-file to do its work, but you do need 
to have run apt-file update before expecting up to date and correct 
answers.

Very similar, I think, to apt-cache search when doing apt-file show but 
with the additional ability to go the other way. For example I just did 
apt-file search bootinfoscript to find out that the file is contained in 
boot-info-script.

Mark

Re: New install Jesse 8.6.0...grub2 problem

[Cindy-Sue Causey]

On 10/30/16, Pascal Hambourg  wrote:
> Le 30/10/2016 à 13:13, Lisi Reisz a écrit :
>> On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:
>>>
>>> The result of bootinfoscript would be a good starting point.
>>
>> I have Jessie fully updated and aptitude can't find bootinfoscript.
>
> How did you search ? It is a command, not a package name. The package
> name is boot-info-script (don't ask me why hyphens were inserted).


I'm going to step out onto a limb and presume she did what I just did,
input "bootinfoscrript" into her preferred Debian package manager and
let 'er rip. In fact, Lisi referenced "aptitude", her preferred
package manager.

For mine, I use "apt-cache search". It returns feedback on anything
you input, not just package names. I a-sume aptitude and others
perform similarly.

When queried via "apt-cache search", "bootinfoscript" received back
zero possibilities here, too. However, querying "boot-info-script" did
return something. One returned possibility:

"boot-info-script - inspect boot environment"

Cool. Will be checking it out.

The hyphens in the middle of the name were likely injected as a
cognitive friendly addition to the name in the same way many other
packages do. I can understand those are a pain when keying them in a
lot. I detest underscores even more.

As a reminder tip for newcomers: When beginning to type in a terminal
command, especially the ones with characters that "annoy" you, one can
start typing the name and then hit the tab key a time or two to be
offered a chance to have the command autocompleted. If there's a list
of commands that start similarly,  you just have to keep trimming
things down by adding more characters (letters, numbers) until the
desired command is the only one left to be autocompleted.

With underscores, it recently crossed my reading path that once in a
great while hyphens and underscores are interchangeable. Haven't had a
situation come up to be able to test that one so it remains a
theoretical #toDo.

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: New install Jesse 8.6.0...grub2 problem

[Lisi Reisz]

On Sunday 30 October 2016 13:32:27 Pascal Hambourg wrote:
> Le 30/10/2016 à 13:13, Lisi Reisz a écrit :
> > On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:
> >> The result of bootinfoscript would be a good starting point.
> >
> > I have Jessie fully updated and aptitude can't find bootinfoscript.
>
> How did you search ? It is a command, not a package name. The package
> name is boot-info-script (don't ask me why hyphens were inserted).

Ah!!  I tried to run it as command, first as my $USER and then as root.  I 
then searched for a package.  I then commented as above.

Now installed and functional.  Will have a good look later.  Thanks.

Lisi

Re: New install Jesse 8.6.0...grub2 problem

[Pascal Hambourg]

Le 30/10/2016 à 13:13, Lisi Reisz a écrit :

On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:


The result of bootinfoscript would be a good starting point.


I have Jessie fully updated and aptitude can't find bootinfoscript.


How did you search ? It is a command, not a package name. The package 
name is boot-info-script (don't ask me why hyphens were inserted).

Re: New install Jesse 8.6.0...grub2 problem

[Lisi Reisz]

On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:
> Le 06/10/2016 à 19:22, Mark Neidorff a écrit :
> > Is there more information that you need to help me?
>
> The result of bootinfoscript would be a good starting point.

I have Jessie fully updated and aptitude can't find bootinfoscript.

Lisi

Re: New install Jesse 8.6.0...grub2 problem

[Felix Miata]

Pascal Hambourg composed on 2016-10-06 20:30 (UTC+0200):


...if the OP followed the openSUSE installer defaults, the root
filesystem is btrfs and can be shrinked while mounted.


That depends on which openSUSE he installed, data he didn't provide. BTRFS 
became default between 13.2 and 42.1 releases.

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: New install Jesse 8.6.0...grub2 problem

[Pascal Hambourg]

Le 06/10/2016 à 20:12, Felix Miata a écrit :


No Linux distro needs more than a tiny fraction of a 750G HD.


Wise people would never use all 750 GB for a single OS if it does not 
need to contain as many data.



Once
booted into Jessie you can shrink the openSUSE installation to a more
reasonable size, leaving yourself room for at least a dozen other
distros in multiboot on your 750G.


Actually if the OP followed the openSUSE installer defaults, the root 
filesystem is btrfs and can be shrinked while mounted.




If all you get is a login prompt, login as root and run os-prober.


os-prober just detects other OS'es, it does not change anything. You 
need to run update-grub (or update-grub2 as openSUSE may name it) to add 
boot menu entries for the discovered OS'es.

Re: New install Jesse 8.6.0...grub2 problem

[Pascal Hambourg]

Le 06/10/2016 à 19:22, Mark Neidorff a écrit :


Is there more information that you need to help me?


The result of bootinfoscript would be a good starting point.

Re: New install Jesse 8.6.0...grub2 problem

[Felix Miata]

Mark Neidorff composed on 2016-10-06 13:22 (UTC-0400):


I'm building a server PC to perform backups of the PCs on my local network.
The server has 2 HDDs--750 Gb and 2 Tb.  The intention is to use the 750 Gb
drive for the OS and the 2 Tb drive for the backup data. I'll get there in
stages.  I'll be using backuppc to do the actual backups.



I tried using a different distro--OpenSUSE and it didn't work out.  I installed
the distro on the 750 Gb drive (and it boots via grub2 from the 750 Gb drive),
but couldn't get backuppc working.  I didn't want to just wipe out the
OpenSUSE installation, so I carved a partition out on the 2Tb data drive and
installed debian there.



The install went fine, up to installing grub2.  The installer didn't find grub2
on the 750Gb drive, and it reported no other OS detected.  I then selected the
2 Tb drive as the boot drive and it errored out when I asked to install grub2
on the 2 Tb drive.  So, I installed grub2 on the 750 Gb drive.



My problem is that when I boot the machine, it boots into OpenSUSE, and
doesn't give me a menu to choose from.


Because when it was installed there was no other OS, so it defaulted to the 
only one, without any timeout or need for a menu.



I don't know how to proceed from here.



My question(s):
Is there more information that you need to help me?


No Linux distro needs more than a tiny fraction of a 750G HD. Once booted 
into Jessie you can shrink the openSUSE installation to a more reasonable 
size, leaving yourself room for at least a dozen other distros in multiboot 
on your 750G. Multiboot also offers the opportunity to perform repairs 
without any rescue media, and test new and/or beta distros without disturbing 
whatever you run normally. The main thing to remember about installing 
multiboot is to let at the very most only one distro to put Grub on the MBR. 
Otherwise, last installed or updated will always overwrite the previous, 
potentially causing no booting at all, similar to what you have now.


cf. http://fm.no-ip.com/PC/install-doz-after.html


How do I go about fixing this boot problem so that I can boot into Debian?


If openSUSE is booting into the GUI, login and use YaST2 to configure the 
bootloader to find and add Jessie to its menu and make it the default boot 
selection. You can change the timeout value to anything you wish.


If all you get is a login prompt, login as root and run os-prober.

see also https://en.opensuse.org/GRUB
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

New install Jesse 8.6.0...grub2 problem

[Mark Neidorff]

Hello,

I'm building a server PC to perform backups of the PCs on my local network.  
The server has 2 HDDs--750 Gb and 2 Tb.  The intention is to use the 750 Gb 
drive for the OS and the 2 Tb drive for the backup data. I'll get there in 
stages.  I'll be using backuppc to do the actual backups.

I tried using a different distro--OpenSUSE and it didn't work out.  I installed 
the distro on the 750 Gb drive (and it boots via grub2 from the 750 Gb drive), 
but couldn't get backuppc working.  I didn't want to just wipe out the 
OpenSUSE installation, so I carved a partition out on the 2Tb data drive and 
installed debian there.  

The install went fine, up to installing grub2.  The installer didn't find grub2 
on the 750Gb drive, and it reported no other OS detected.  I then selected the 
2 Tb drive as the boot drive and it errored out when I asked to install grub2 
on the 2 Tb drive.  So, I installed grub2 on the 750 Gb drive.

My problem is that when I boot the machine, it boots into OpenSUSE, and 
doesn't give me a menu to choose from.

I don't know how to proceed from here.

My question(s):
Is there more information that you need to help me?

How do I go about fixing this boot problem so that I can boot into Debian?

Many thanks,

Mark

New install of Jesse for backuppc use

[Mark Neidorff]

It has been about 7 years since I've been on the list.

I decided to implement a comprehensive backup solution and chose backuppc.  I 
also built a new mini-ITX PC for this use--Intel Core i3, 8 Gb RAM, 750 GB 
HDD, wired networking---and Debian Jesse for the software.  To be fair, before 
I decided to build this computer, I installed Raspbian on my Raspberry Pi 2 
and used that to test backuppc.  All went well. (except backup times were 
horribly slow due to the design of the Pi).

So, I installed Jesse yesterday, made sure everything is up to date, and then 
installed the debian version of backuppc.  All seemed to go well.  

I took note--wrote down--the backuppc user name and password.  I tried to log 
in, but backuppc kept telling me that I had the wrong password.  

So, I followed the directions to change the password.  That "seemed" to work, 
but when I log in, it wants to download a file, rather than log me in to the 
backuppc "console".  I tried several times.  Same result.  I shut the PC down 
and started it back up, same result.

Does anyone have an idea why this is happening and the steps that I need to go 
through to fix it?

Many thanks,

Mark

Re: New Install Fails at Step 14

[Steve Matzura]

That's quite all right, it's not something that's really important
unless the non-full installs don't include screenreader support
durinig the actual install, which they probably don't. You don't even
have to ask your friend. If you happen to have a copy of the distro
handy, boot it, and tell me if there's an option to start the
installation with a screenreader, which is documented in the full
install as the "S" option on the install menu.


On Wed, 30 Dec 2015 15:49:35 +, you wrote:

>On Wednesday 30 December 2015 15:39:37 Steve Matzura wrote:
>> Step 14 is "Install additional software." If the net install works
>> with speech, then I can do it. Without speech output from the built-in
>> screenreader, it's of no use to me without sighted assistance, which I
>> do not have.
>
>Sorry.  I hadn't taken in that you couldn't see.  I have a blind friend who 
>installs Debian periodically.  I'll ask him exactly how he does it.
>
>Lisi
>
>>
>> On Thu, 31 Dec 2015 04:28:52 +1300, you wrote:
>> >On Wed, Dec 30, 2015 at 10:22:30AM -0500, Steve Matzura wrote:
>> >> So since my installation is virgin and is failing at Step 14, should I
>> >> just start again and see if I get any further this time, or is there
>> >> anything I should choose or specify differently when trying again?
>> >
>> >I don't know what step 14 is, but you could just use the netinst CD and
>> >install from the net.
>

Re: New Install Fails at Step 14

[Steve Matzura]

Step 14 is "Install additional software." If the net install works
with speech, then I can do it. Without speech output from the built-in
screenreader, it's of no use to me without sighted assistance, which I
do not have.

On Thu, 31 Dec 2015 04:28:52 +1300, you wrote:

>On Wed, Dec 30, 2015 at 10:22:30AM -0500, Steve Matzura wrote:
>> So since my installation is virgin and is failing at Step 14, should I
>> just start again and see if I get any further this time, or is there
>> anything I should choose or specify differently when trying again?
>
>I don't know what step 14 is, but you could just use the netinst CD and
>install from the net.

Re: New Install Fails at Step 14

[Lisi Reisz]

On Wednesday 30 December 2015 16:06:54 Steve Matzura wrote:
> That's quite all right, it's not something that's really important
> unless the non-full installs don't include screenreader support
> durinig the actual install, which they probably don't. You don't even
> have to ask your friend. If you happen to have a copy of the distro
> handy, boot it, and tell me if there's an option to start the
> installation with a screenreader, which is documented in the full
> install as the "S" option on the install menu.

I have already asked him.  Here is my question and his reply:

-
Can the Debian net-install be done with sound?



Yes.  After the beep I think it's control+S and return.  Sometimes it
speaks very quietly but it does speak.  Quite slowly.

I can write more if you need it.



Let me know if you would like more!

Lisi

>
> On Wed, 30 Dec 2015 15:49:35 +, you wrote:
> >On Wednesday 30 December 2015 15:39:37 Steve Matzura wrote:
> >> Step 14 is "Install additional software." If the net install works
> >> with speech, then I can do it. Without speech output from the built-in
> >> screenreader, it's of no use to me without sighted assistance, which I
> >> do not have.
> >
> >Sorry.  I hadn't taken in that you couldn't see.  I have a blind friend
> > who installs Debian periodically.  I'll ask him exactly how he does it.
> >
> >Lisi
> >
> >> On Thu, 31 Dec 2015 04:28:52 +1300, you wrote:
> >> >On Wed, Dec 30, 2015 at 10:22:30AM -0500, Steve Matzura wrote:
> >> >> So since my installation is virgin and is failing at Step 14, should
> >> >> I just start again and see if I get any further this time, or is
> >> >> there anything I should choose or specify differently when trying
> >> >> again?
> >> >
> >> >I don't know what step 14 is, but you could just use the netinst CD and
> >> >install from the net.

Re: New Install Fails at Step 14

[Lisi Reisz]

On Wednesday 30 December 2015 15:39:37 Steve Matzura wrote:
> Step 14 is "Install additional software." If the net install works
> with speech, then I can do it. Without speech output from the built-in
> screenreader, it's of no use to me without sighted assistance, which I
> do not have.

Sorry.  I hadn't taken in that you couldn't see.  I have a blind friend who 
installs Debian periodically.  I'll ask him exactly how he does it.

Lisi

>
> On Thu, 31 Dec 2015 04:28:52 +1300, you wrote:
> >On Wed, Dec 30, 2015 at 10:22:30AM -0500, Steve Matzura wrote:
> >> So since my installation is virgin and is failing at Step 14, should I
> >> just start again and see if I get any further this time, or is there
> >> anything I should choose or specify differently when trying again?
> >
> >I don't know what step 14 is, but you could just use the netinst CD and
> >install from the net.

Re: New Install Fails at Step 14

[Steve Matzura]

So since my installation is virgin and is failing at Step 14, should I
just start again and see if I get any further this time, or is there
anything I should choose or specify differently when trying again?

Re: New Install Fails at Step 14

[Chris Bannister]

On Wed, Dec 30, 2015 at 10:22:30AM -0500, Steve Matzura wrote:
> So since my installation is virgin and is failing at Step 14, should I
> just start again and see if I get any further this time, or is there
> anything I should choose or specify differently when trying again?

I don't know what step 14 is, but you could just use the netinst CD and
install from the net.

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X