Re: balenaEtcher installation problem

[Timothy M Butterworth]

On Thu, Nov 9, 2023 at 11:21 PM Gary L. Roach 
wrote:

> Hi all
>
> Operating System: Debian GNU/Linux 12
> KDE Plasma Version: 5.27.5
> KDE Frameworks Version: 5.103.0
> Qt Version: 5.15.8
> Kernel Version: 6.1.0-13-amd64 (64-bit)
> Graphics Platform: Wayland
> Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
> Memory: 31.2 GiB of RAM
> Graphics Processor: AMD CAICOS
> Manufacturer: MSI
> Product Name: MS-7974
> System Version: 1.0
>
> I have been trying to install the balenaEtcher software package 
> *balenaEtcher-1.18.11-x64.AppImage
> *for 2 days without success. I keep getting the following error:
>
>
> *ERROR:ozone_platform_x11.cc(247)] Missing X server or $DISPLAY
> [10145:1109/120137.666202:ERROR:env.cc(226)] The platform failed to
> initialize.  Exiting*
>
>
You currently are running on Wayland. You need to install X11 because the
app can not run on Wayland.

sudo apt install xwayland


> I have been searching the internet for solutions and have found many
> listings but none of them work. My $DISPLAY variable is empty which may be
> the source of the problem but what should it hold? I am using the .deb file
> downloaded from the balena web sight. Sorry if this information is a bit
> sketchy but is the best I can do at this point.
>
> Any help on this problem will be sincerely appreciated. i really need a
> package that can handle burning .iso files to SD cards and this seems to be
> the best out there.
>
> Gary R
>
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: balenaEtcher installation problem

[Jeffrey Walton]

On Thu, Nov 9, 2023 at 9:01 PM Gary L. Roach  wrote:
>
> Operating System: Debian GNU/Linux 12
> KDE Plasma Version: 5.27.5
> KDE Frameworks Version: 5.103.0
> Qt Version: 5.15.8
> Kernel Version: 6.1.0-13-amd64 (64-bit)
> Graphics Platform: Wayland
> Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
> Memory: 31.2 GiB of RAM
> Graphics Processor: AMD CAICOS
> Manufacturer: MSI
> Product Name: MS-7974
> System Version: 1.0
>
> I have been trying to install the balenaEtcher software package 
> balenaEtcher-1.18.11-x64.AppImage for 2 days without success. I keep getting 
> the following error:
>
> ERROR:ozone_platform_x11.cc(247)] Missing X server or $DISPLAY
> [10145:1109/120137.666202:ERROR:env.cc(226)] The platform failed to 
> initialize.  Exiting
>
> I have been searching the internet for solutions and have found many listings 
> but none of them work. My $DISPLAY variable is empty which may be the source 
> of the problem but what should it hold? I am using the .deb file downloaded 
> from the balena web sight. Sorry if this information is a bit sketchy but is 
> the best I can do at this point.
>
> Any help on this problem will be sincerely appreciated. i really need a 
> package that can handle burning .iso files to SD cards and this seems to be 
> the best out there.

Try `export DISPLAY=":0.0"`.

Jeff

balenaEtcher installation problem

[Gary L. Roach]

Hi all

Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-13-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD CAICOS
Manufacturer: MSI
Product Name: MS-7974
System Version: 1.0

I have been trying to install the balenaEtcher software package 
*balenaEtcher-1.18.11-x64.AppImage *for 2 days without success. I keep 
getting the following error:


*ERROR:ozone_platform_x11.cc(247)] Missing X server or $DISPLAY
[10145:1109/120137.666202:ERROR:env.cc(226)] The platform failed to 
initialize.  Exiting*


I have been searching the internet for solutions and have found many 
listings but none of them work. My $DISPLAY variable is empty which may 
be the source of the problem but what should it hold? I am using the 
.deb file downloaded from the balena web sight. Sorry if this 
information is a bit sketchy but is the best I can do at this point.


Any help on this problem will be sincerely appreciated. i really need a 
package that can handle burning .iso files to SD cards and this seems to 
be the best out there.


Gary R

*
*

Re: Netgen installation problem

[Charles Curley]

On Thu, 26 May 2022 11:31:53 -0700
"Gary L. Roach"  wrote:

> It is interesting that running netgen 
> from the command line doesn't work but the icon on the desktop does.

Often when I see this I will go through the relevant desktop file and
look for clues. In this case, it is probably netgen.desktop. So
something like:

less -X $(locate netgen.desktop)

(Assuming there's only one copy of netgen.desktop on the system.)

You've already solved your problem, but this may help some future
reader.

-- 
Does anybody read signatures any more?

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

Re: Netgen installation problem

[Gary L. Roach]

Thanks Anssi

I made sure that the PATH's matched what you did and ran the program 
from the desktop. It worked fine. It is interesting that running netgen 
from the command line doesn't work but the icon on the desktop does. I 
never noticed this before but may have just missed it. After 20 years of 
using Debian you would think that I would have stumbled across this 
before. Thanks again. Problem solved.


Gary R

On 5/25/22 11:20 AM, Anssi Saari wrote:

NETGENDIR=/usr/share/netgen /usr/bin/netgen

Re: Netgen installation problem

[Anssi Saari]

"Gary L. Roach"  writes:

> Thanks for the reply Tomas,
>
> Running the apt-file search libgui.so search now gets the exact same results 
> as your search. Unfortunately,
> running netgen still gives the same error message. Now what?

Maybe a hint: apt-file search doesn't list files that're installed so
the advice from Tomas is still valid.

However, it did actually show one problem:

libnglib-dev: /usr/lib/x86_64-linux-gnu/netgen/libgui.so

Meaning, you need libnglib-dev for libgui.so. And then you need to run
netgen the way the packaged .desktop file does it:

LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/netgen NETGENDIR=/usr/share/netgen 
/usr/bin/netgen

At least I got a GUI window after that. I don't know how to actually use
netgen though.

Re: Netgen installation problem

[tomas]

On Wed, May 25, 2022 at 10:48:28AM -0700, Gary L. Roach wrote:
> Thanks for the reply Tomas,
> 
> Running the _/apt-file search libgui.so/_ search now gets the exact same
> results as your search. Unfortunately, running netgen still gives the same
> error message. Now what?

Is libgui.so there? It's probably a symlink. Is it pointing
to something?

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Netgen installation problem

[Gary L. Roach]

Thanks for the reply Tomas,

Running the _/apt-file search libgui.so/_ search now gets the exact same 
results as your search. Unfortunately, running netgen still gives the 
same error message. Now what?


Gary R


On 5/24/22 10:37 PM, to...@tuxteam.de wrote:

On Tue, May 24, 2022 at 02:40:09PM -0700, Gary L. Roach wrote:

Hi all,

Operating System: Debian GNU/Linux 11
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.0-13-amd64
OS Type: 64-bit
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD CAICOS

I have installed netgen from the Debian Bullseye package library. When I run
the program I get the following error message:

/gary@debian:~/Netgen/build$ netgen//
//NETGEN-6.2-dev//
//Developed by Joachim Schoeberl at//
//2010- Vienna University of Technology//
//2006-2010 RWTH Aachen University//
//1996-2006 Johannes Kepler University Linz//
//Including OpenCascade geometry kernel//
//Including MPI version 3.1//
//Error in Tcl-Script://
//result = couldn't load file "libgui.so": libgui.so: cannot open shared
object file: No such file or directory//
//
//Make sure to set environment variable NETGENDIR to directory containing
ng.tcl/

/
/

/There is not ng.tcl or libgui.so on my system so it is hard to set
NETGENDIR when I can't find the files. I used locate to try to find the file
but no luck. Any suggestions?/

   tomas@trotzki:~$ apt-file search libgui.so
   libnglib-6.2: /usr/lib/x86_64-linux-gnu/netgen/libgui.so.6.2
   libnglib-6.2: /usr/lib/x86_64-linux-gnu/netgen/libgui.so.6.2.1905
   libnglib-dev: /usr/lib/x86_64-linux-gnu/netgen/libgui.so
   libsight: /usr/lib/x86_64-linux-gnu/sight/gui-0.1/libgui.so.0
   libsight: /usr/lib/x86_64-linux-gnu/sight/gui-0.1/libgui.so.0.1

Next stop seems to be to check whether libnglib-6.2 is installed in
your system and whether /usr/lib/x86_64-linux-gnu/netgen/libgui.so.6.2
is there and points to something existent, too.

Cheers

Re: Netgen installation problem

[tomas]

On Tue, May 24, 2022 at 02:40:09PM -0700, Gary L. Roach wrote:
> Hi all,
> 
> Operating System: Debian GNU/Linux 11
> KDE Plasma Version: 5.20.5
> KDE Frameworks Version: 5.78.0
> Qt Version: 5.15.2
> Kernel Version: 5.10.0-13-amd64
> OS Type: 64-bit
> Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
> Memory: 15.6 GiB of RAM
> Graphics Processor: AMD CAICOS
> 
> I have installed netgen from the Debian Bullseye package library. When I run
> the program I get the following error message:
> 
> /gary@debian:~/Netgen/build$ netgen//
> //NETGEN-6.2-dev//
> //Developed by Joachim Schoeberl at//
> //2010- Vienna University of Technology//
> //2006-2010 RWTH Aachen University//
> //1996-2006 Johannes Kepler University Linz//
> //Including OpenCascade geometry kernel//
> //Including MPI version 3.1//
> //Error in Tcl-Script://
> //result = couldn't load file "libgui.so": libgui.so: cannot open shared
> object file: No such file or directory//
> //
> //Make sure to set environment variable NETGENDIR to directory containing
> ng.tcl/
> 
> /
> /
> 
> /There is not ng.tcl or libgui.so on my system so it is hard to set
> NETGENDIR when I can't find the files. I used locate to try to find the file
> but no luck. Any suggestions?/

  tomas@trotzki:~$ apt-file search libgui.so
  libnglib-6.2: /usr/lib/x86_64-linux-gnu/netgen/libgui.so.6.2
  libnglib-6.2: /usr/lib/x86_64-linux-gnu/netgen/libgui.so.6.2.1905
  libnglib-dev: /usr/lib/x86_64-linux-gnu/netgen/libgui.so
  libsight: /usr/lib/x86_64-linux-gnu/sight/gui-0.1/libgui.so.0
  libsight: /usr/lib/x86_64-linux-gnu/sight/gui-0.1/libgui.so.0.1

Next stop seems to be to check whether libnglib-6.2 is installed in
your system and whether /usr/lib/x86_64-linux-gnu/netgen/libgui.so.6.2
is there and points to something existent, too.

Cheers
-- 
t


signature.asc
Description: PGP signature

Netgen installation problem

[Gary L. Roach]

Hi all,

Operating System: Debian GNU/Linux 11
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.0-13-amd64
OS Type: 64-bit
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD CAICOS

I have installed netgen from the Debian Bullseye package library. When I 
run the program I get the following error message:


/gary@debian:~/Netgen/build$ netgen//
//NETGEN-6.2-dev//
//Developed by Joachim Schoeberl at//
//2010- Vienna University of Technology//
//2006-2010 RWTH Aachen University//
//1996-2006 Johannes Kepler University Linz//
//Including OpenCascade geometry kernel//
//Including MPI version 3.1//
//Error in Tcl-Script://
//result = couldn't load file "libgui.so": libgui.so: cannot open shared 
object file: No such file or directory//

//
//Make sure to set environment variable NETGENDIR to directory 
containing ng.tcl/


/
/

/There is not ng.tcl or libgui.so on my system so it is hard to set 
NETGENDIR when I can't find the files. I used locate to try to find the 
file but no luck. Any suggestions?/


/Gary R/

Re: TexMaker installation problem

[Curt]

On 2022-03-20, Grzesiek  wrote:
> Hi there, please fix the following:
>
> # apt install texmaker
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following package was automatically installed and is no longer required:
>libigdgmm12
> Use 'apt autoremove' to remove it.
> Suggested packages:
>texlive-lang-all
> Recommended packages:
>asymptote
> The following NEW packages will be installed:
>texmaker
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/4440 kB of archives.
> After this operation, 10.8 MB of additional disk space will be used.
> (Reading database ... 209748 files and directories currently installed.)
> Preparing to unpack .../texmaker_5.1.2+dfsg-1_amd64.deb ...
> Unpacking texmaker (5.1.2+dfsg-1) ...
> dpkg: error processing archive /tmp/texmaker_5.1.2+dfsg-1_amd64.deb 
> (--unpack):
>   trying to overwrite '/usr/share/pixmaps/texmaker.png', which is also 
> in package texmaker-data 5.1.2+dfsg-1
> Errors were encountered while processing:
>   /tmp/texmaker_5.1.2+dfsg-1_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>

It seems to be a bug that has been fixed in the latest version of
texmaker.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007149

- 

TexMaker installation problem

[Grzesiek]

Hi there, please fix the following:

# apt install texmaker
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  libigdgmm12
Use 'apt autoremove' to remove it.
Suggested packages:
  texlive-lang-all
Recommended packages:
  asymptote
The following NEW packages will be installed:
  texmaker
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/4440 kB of archives.
After this operation, 10.8 MB of additional disk space will be used.
(Reading database ... 209748 files and directories currently installed.)
Preparing to unpack .../texmaker_5.1.2+dfsg-1_amd64.deb ...
Unpacking texmaker (5.1.2+dfsg-1) ...
dpkg: error processing archive /tmp/texmaker_5.1.2+dfsg-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/pixmaps/texmaker.png', which is also 
in package texmaker-data 5.1.2+dfsg-1

Errors were encountered while processing:
 /tmp/texmaker_5.1.2+dfsg-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Re: Bullseye installation problem (with Matrox GPU)

[Stefan Monnier]

> I did a little more experimenting and learned my G550 doesn't need
> nomodeset for the MGA X driver to work, but it only produces 1920x1080
> on my 2560x1440 screen, and xrandr still can't identify output names.

You can trying playing with "modelines" where you reduce the screen
refresh rate to 30Hz to keep the "dot frequency" below the card's limit.

Contrary to CRT, current displays tend not to need as high a refresh
rate to avoid flicker.  Of course a lower refresh rate may encounter
other problems (e.g. your display may simply refuse to display it).


Stefan

Re: Bullseye installation problem (with Matrox GPU)

[Dan Ritter]

Felix Miata wrote: 
> > https://www.phoronix.com/scan.php?page=news_item=Linux-5.10-Matrox-G200  
> > 
> I did a little more experimenting and learned my G550 doesn't need nomodeset 
> for
> the MGA X driver to work, but it only produces 1920x1080 on my 2560x1440 
> screen,
> and xrandr still can't identify output names.

I believe that the DAC on the G550 is only good up to 2048x1536
(DVI) or 1600x1200 (VGA).

It was pretty good when it was introduced 20 years ago, and not
too bad when the PCIe version was made 15 years ago.


-dsr-

Re: Bullseye installation problem (with Matrox GPU)

[Felix Miata]

Andrew M.A. Cater composed on 2021-07-06 22:30 (UTC):

> On Tue, Jul 06, 2021 at 04:26:52PM -0400, Felix Miata wrote:

>> I do have the MGA driver xserver-xorg-video-mga dysfunctional on (an AGP) 
>> G550 in
>> i686 Bullseye by disabling KMS via nomodeset on, and adding iomem=relaxed 
>> to, the
>> kernel command line, without installing firmware-misc-nonfree. The 
>> dysfunction is
>> the screen blanks momentarily at random times, but is otherwise normal as 
>> long as
>> xrandr is not needed to configure the screen. Installing 
>> firmware-misc-nonfree
>> doesn't help.

> Good news, then - apparently 5.10 now supports this better with KMS and will
> also support the non-server G200 on Matrox cards

> https://www.phoronix.com/scan.php?page=news_item=Linux-5.10-Matrox-G200
> 
I did a little more experimenting and learned my G550 doesn't need nomodeset for
the MGA X driver to work, but it only produces 1920x1080 on my 2560x1440 screen,
and xrandr still can't identify output names.

# lsmod | egrep 'mga|video'
# xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 400 x 270, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
   1920x1080 60.00*
# inxi -SGay
System:
  Host: a-865.ij.net Kernel: 5.10.0-7-686 i686 bits: 32 compiler: gcc
  v: 10.2.1
  parameters:...noresume mitigations=auto consoleblank=0 iomem=relaxed
  Desktop: Trinity R14.0.11 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 vt: 3
  dm: startx Distro: Debian GNU/Linux 11 (bullseye)
Graphics:
  Device-1: Matrox Systems Millennium G550 driver: N/A
  alternate: matroxfb_base bus-ID: 01:00.0 chip-ID: 102b:2527 class-ID: 0300
  Display: server: X.Org 1.20.11 driver: loaded: mga
  unloaded: fbdev,modesetting,vesa display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 81 s-size: 602x343mm (23.7x13.5")
  s-diag: 693mm (27.3")
  Monitor-1: default res: 1920x1080 hz: 60
  OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.4
  compat-v: 3.1 direct render: Yes
# lsmod | egrep -i 'mga|video'
#
-- 
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: Bullseye installation problem (with Matrox GPU)

[Andrew M.A. Cater]

On Tue, Jul 06, 2021 at 04:26:52PM -0400, Felix Miata wrote:
> Andrew M.A. Cater composed on 2021-07-06 12:56 (UTC):
> 
> > Try installing firmware-misc-nonfree which will pull in 
> > firmware-amd-graphics
> > I think.
> 
> > I normally install firmware-linux-free firmware-linux-nonfree 
> > firmware-misc-nonfree - that covers all bases.
> 
> > The AMD firmware is not in the standard firmware-linux-nonfree, from memory.
> 
> > It's installed on my HP Microserver which is also Matrox G200
>   
> 
> Matrox has absolutely nothing to do with AMD except that they both "provide"
> (manufacture?) graphics devices. If your HP G200e is working, then so should
> Chris' be able to as well.
> 
You may be right - but I found that installing the AMD frimware solved
something for me. I've two HP Microserver Gen 8 machines here. Fonts
maybe.

> The G200e is a special evolution of the original G200/G400/G450/G550/G650 
> series
> that last I knew was no longer supported upstream since KMS matured. AFAIK, 
> the
> G200e was supposedly the only chip supported by MGA X driver patches intended 
> to
> keep X viable on HP servers without anyone willing to provide kernel support 
> for
> KMS on Matrox.
> 
> I do have the MGA driver xserver-xorg-video-mga dysfunctional on (an AGP) 
> G550 in
> i686 Bullseye by disabling KMS via nomodeset on, and adding iomem=relaxed to, 
> the
> kernel command line, without installing firmware-misc-nonfree. The 
> dysfunction is
> the screen blanks momentarily at random times, but is otherwise normal as 
> long as
> xrandr is not needed to configure the screen. Installing firmware-misc-nonfree
> doesn't help.
> -- 
> 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
> 

Good news, then - apparently 5.10 now supports this better with KMS and will
also support the non-server G200 on Matrox cards

https://www.phoronix.com/scan.php?page=news_item=Linux-5.10-Matrox-G200

All the best, as ever,

Andy Cater

Re: Bullseye installation problem (with Matrox GPU)

[Felix Miata]

Andrew M.A. Cater composed on 2021-07-06 12:56 (UTC):

> Try installing firmware-misc-nonfree which will pull in firmware-amd-graphics
> I think.

> I normally install firmware-linux-free firmware-linux-nonfree 
> firmware-misc-nonfree - that covers all bases.

> The AMD firmware is not in the standard firmware-linux-nonfree, from memory.

> It's installed on my HP Microserver which is also Matrox G200


Matrox has absolutely nothing to do with AMD except that they both "provide"
(manufacture?) graphics devices. If your HP G200e is working, then so should
Chris' be able to as well.

The G200e is a special evolution of the original G200/G400/G450/G550/G650 series
that last I knew was no longer supported upstream since KMS matured. AFAIK, the
G200e was supposedly the only chip supported by MGA X driver patches intended to
keep X viable on HP servers without anyone willing to provide kernel support for
KMS on Matrox.

I do have the MGA driver xserver-xorg-video-mga dysfunctional on (an AGP) G550 
in
i686 Bullseye by disabling KMS via nomodeset on, and adding iomem=relaxed to, 
the
kernel command line, without installing firmware-misc-nonfree. The dysfunction 
is
the screen blanks momentarily at random times, but is otherwise normal as long 
as
xrandr is not needed to configure the screen. Installing firmware-misc-nonfree
doesn't help.
-- 
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: Bullseye installation problem

[Chris Bell]

On Tuesday, 6 July 2021 11:45:10 BST you wrote:
> Thanks for the reply
> 
> > Machine HP Proliant ML150 with 5GB RAM and currently a single HDD. I
> 
> normally
> 
> > use a netinst CD created locally from the jigdo image (amd64).
> > I have tried to install both basic bullseye rc1 and bullseye rc2 with SSH
> > server several times over the last few days, using different netinst CD's,
> 
> and
> 
> > each time the installation appears to be faultless until I try to boot the
> 
> new
> 
> > installation. I just want to be able to login locally, do a small amount
> > of
> > configuration, and then login remotely over the network. The GRUB display
> > is normal, but then the SVGA monitor only shows a single message about
> > 
> > VMX outside text (disabled by BIOS)
> > 
> > before the monitor complains that the video is out of range and gives
> > up
> > 
> > Is firmware for your graphics device installed?
> 
> I always use the "unofficial" installer with firmware, so it was
> 
> firmware-bullseye-DI-rc2-amd64-netinst.iso
> 
> and
> 
> firmware-bullseye-DI-rc2-amd64-i386-netinst.iso
> 
> > Try working around the immediate problem by appending nomodeset to the
> > kernel command line via E key at Grub menu. For most graphics chips,
> > nomodeset blocks a requirement of most AMD, Intel and NVidia GPUs X
> > drivers, enabled KMS, so using it is little but a crutch to enable
> > reconfiguration and troubleshooting [1].
> > 
> > What is output from
> > 
> > lspci -nnk | grep -A3 VGA
> 
>  This is the output from the working buster 10.10.0 installation:
>  lspci -nnk | grep -A3 VGA
> 0a:02.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd.
> MGA G200e [Pilot] ServerEngines (SEP1) [102b:0522] (rev 02)
> Subsystem: Hewlett-Packard Company ProLiant DL140 G3 [103c:31fa]
> Kernel driver in use: mgag200
> Kernel modules: mgag200
> 
> I am not desperate to get bullseye installed at the moment as I can still
> use buster 10.10.0, but the release team want to prepare the full release
> soon. I see that someone has already reported an issue with (I think) a
> virtual different HP machine, which may not be identical.
> I have full access (from the running buster 10.10.0 installation) to / for
> the rc2 installation, including all the logs from the boot attempt, but all
> I could do at the time was to select a Ctl-Alt-f3 terminal, login blind as
> root, and do a shutdown.
> I can even swap discs and re-install 10.10.0 to use the machine to avoid re-
> formatting any of the current partitions, which would change UUID's for the
> current 10.10.0, swapping the discs back for further testing.

> The AMD firmware is not in the standard firmware-linux-nonfree, from memory.

> All best,

> Andy C.

> It's installed on my HP Microserver which is also Matrox G200

Thanks for the info, I have assumed no op, hopefully re-installed again for 
the last time, and done some remote admin.

Re: Bullseye installation problem

[Andrew M.A. Cater]

On Tue, Jul 06, 2021 at 11:45:10AM +0100, Chris Bell wrote:
> Thanks for the reply
> 
> > Machine HP Proliant ML150 with 5GB RAM and currently a single HDD. I 
> normally 
> > use a netinst CD created locally from the jigdo image (amd64).
> > I have tried to install both basic bullseye rc1 and bullseye rc2 with SSH 
> > server several times over the last few days, using different netinst CD's, 
> and 
> > each time the installation appears to be faultless until I try to boot the 
> new 
> > installation. I just want to be able to login locally, do a small amount of 
> > configuration, and then login remotely over the network. The GRUB display 
> > is 
> > normal, but then the SVGA monitor only shows a single message about
> 
> > VMX outside text (disabled by BIOS)
> 
> > before the monitor complains that the video is out of range and gives up
>   
> 
> > Is firmware for your graphics device installed?
> 
> I always use the "unofficial" installer with firmware, so it was
> 
> firmware-bullseye-DI-rc2-amd64-netinst.iso
> 
> and
> 
> firmware-bullseye-DI-rc2-amd64-i386-netinst.iso
> 
> > Try working around the immediate problem by appending nomodeset to the
> > kernel command line via E key at Grub menu. For most graphics chips,
> > nomodeset blocks a requirement of most AMD, Intel and NVidia GPUs X
> > drivers, enabled KMS, so using it is little but a crutch to enable
> > reconfiguration and troubleshooting [1].
> 
> > What is output from
> > lspci -nnk | grep -A3 VGA
> 
>  This is the output from the working buster 10.10.0 installation:
>  lspci -nnk | grep -A3 VGA
> 0a:02.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA 
> G200e [Pilot] ServerEngines (SEP1) [102b:0522] (rev 02)
> Subsystem: Hewlett-Packard Company ProLiant DL140 G3 [103c:31fa]
> Kernel driver in use: mgag200
> Kernel modules: mgag200
> 
> I am not desperate to get bullseye installed at the moment as I can still use 
> buster 10.10.0, but the release team want to prepare the full release soon.
> I see that someone has already reported an issue with (I think) a virtual 
> different HP machine, which may not be identical.
> I have full access (from the running buster 10.10.0 installation) to / for 
> the 
> rc2 installation, including all the logs from the boot attempt, but all I 
> could do at the time was to select a Ctl-Alt-f3 terminal, login blind as 
> root, 
> and do a shutdown.
> I can even swap discs and re-install 10.10.0 to use the machine to avoid re-
> formatting any of the current partitions, which would change UUID's for the 
> current 10.10.0, swapping the discs back for further testing.
> 
> 
Try installing firmware-misc-nonfree which will pull in firmware-amd-graphics
I think.

I normally install firmware-linux-free firmware-linux-nonfree 
firmware-misc-nonfree - that covers all bases.

The AMD firmware is not in the standard firmware-linux-nonfree, from memory.

All best,

Andy C.

It's installed on my HP Microserver which is also Matrox G200

Andy C.

Re: Bullseye installation problem

[Chris Bell]

Thanks for the reply

> Machine HP Proliant ML150 with 5GB RAM and currently a single HDD. I 
normally 
> use a netinst CD created locally from the jigdo image (amd64).
> I have tried to install both basic bullseye rc1 and bullseye rc2 with SSH 
> server several times over the last few days, using different netinst CD's, 
and 
> each time the installation appears to be faultless until I try to boot the 
new 
> installation. I just want to be able to login locally, do a small amount of 
> configuration, and then login remotely over the network. The GRUB display is 
> normal, but then the SVGA monitor only shows a single message about

> VMX outside text (disabled by BIOS)

> before the monitor complains that the video is out of range and gives up


> Is firmware for your graphics device installed?

I always use the "unofficial" installer with firmware, so it was

firmware-bullseye-DI-rc2-amd64-netinst.iso

and

firmware-bullseye-DI-rc2-amd64-i386-netinst.iso

> Try working around the immediate problem by appending nomodeset to the
> kernel command line via E key at Grub menu. For most graphics chips,
> nomodeset blocks a requirement of most AMD, Intel and NVidia GPUs X
> drivers, enabled KMS, so using it is little but a crutch to enable
> reconfiguration and troubleshooting [1].

> What is output from
>   lspci -nnk | grep -A3 VGA

 This is the output from the working buster 10.10.0 installation:
 lspci -nnk | grep -A3 VGA
0a:02.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA 
G200e [Pilot] ServerEngines (SEP1) [102b:0522] (rev 02)
Subsystem: Hewlett-Packard Company ProLiant DL140 G3 [103c:31fa]
Kernel driver in use: mgag200
Kernel modules: mgag200

I am not desperate to get bullseye installed at the moment as I can still use 
buster 10.10.0, but the release team want to prepare the full release soon.
I see that someone has already reported an issue with (I think) a virtual 
different HP machine, which may not be identical.
I have full access (from the running buster 10.10.0 installation) to / for the 
rc2 installation, including all the logs from the boot attempt, but all I 
could do at the time was to select a Ctl-Alt-f3 terminal, login blind as root, 
and do a shutdown.
I can even swap discs and re-install 10.10.0 to use the machine to avoid re-
formatting any of the current partitions, which would change UUID's for the 
current 10.10.0, swapping the discs back for further testing.

Re: Bullseye installation problem

[Felix Miata]

Chris Bell composed on 2021-07-05 18:22 (UTC+0100):

> Machine HP Proliant ML150 with 5GB RAM and currently a single HDD. I normally 
> use a netinst CD created locally from the jigdo image (amd64).
> I have tried to install both basic bullseye rc1 and bullseye rc2 with SSH 
> server several times over the last few days, using different netinst CD's, 
> and 
> each time the installation appears to be faultless until I try to boot the 
> new 
> installation. I just want to be able to login locally, do a small amount of 
> configuration, and then login remotely over the network. The GRUB display is 
> normal, but then the SVGA monitor only shows a single message about

> VMX outside text (disabled by BIOS)

> before the monitor complains that the video is out of range and gives up


Is firmware for your graphics device installed?

Try working around the immediate problem by appending nomodeset to the
kernel command line via E key at Grub menu. For most graphics chips,
nomodeset blocks a requirement of most AMD, Intel and NVidia GPUs X
drivers, enabled KMS, so using it is little but a crutch to enable
reconfiguration and troubleshooting [1].

What is output from
lspci -nnk | grep -A3 VGA

[1]
https://en.opensuse.org/SDB:Nomodeset:_Work_Around_Graphic_Upgrade_&_Installation_Obstacles
-- 
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

Bullseye installation problem

[Chris Bell]

Hello,
Machine HP Proliant ML150 with 5GB RAM and currently a single HDD. I normally 
use a netinst CD created locally from the jigdo image (amd64).
I have tried to install both basic bullseye rc1 and bullseye rc2 with SSH 
server several times over the last few days, using different netinst CD's, and 
each time the installation appears to be faultless until I try to boot the new 
installation. I just want to be able to login locally, do a small amount of 
configuration, and then login remotely over the network. The GRUB display is 
normal, but then the SVGA monitor only shows a single message about

VMX outside text (disabled by BIOS)

before the monitor complains that the video is out of range and gives up.
This happens with two different monitors.
I have now installed buster 10.10.0 with KDE into a spare partition with full 
access to the 
rc2 partition (including remote access) so am able to copy any information 
required for a bug report, but what should it be reported to?
My only comment about the 10.10.0 installation so far is that a local monitor 
display apears to show a low definition display, with everything including text 
slightly large on the screen, but it appears to work normally.

-- 
Chris Bell
www.chrisbell.org.uk

Re: Docker installation problem

[Robbi Nespu]

On 7/4/21 7:17 AM, Gary L. Roach wrote:
I have been trying to get a working installation of Docker. This should 
be easy considering all of the information available. Alas, for me, this 
doesn't seem to be the case. My latest attempt was to use the 
instructions at 
*https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-debian-10* 
. I followed the instructions to the letter with the exception of 
skipping over the repository setup that I installed before. I got the 
following:


what is on your repos? Mine are:

$ grep "docker" /etc/apt/sources.list
deb [arch=amd64] https://download.docker.com/linux/debian/ bullseye stable

and docker are working fine. I use it for my springboot development to 
host database.



--
Robbi Nespu 
D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
https://robbinespu.gitlab.io | https://mstdn.social/@robbinespu

Re: Docker installation problem

[Greg Wooledge]

On Sat, Jul 03, 2021 at 05:30:18PM -0700, Gary L. Roach wrote:
> What tipped
> you off?

Probably this:

> > > > /Could not connect to any X display./
> > > > debconf: unable to initialize frontend: Kde

Re: Docker installation problem

[Gary L. Roach]

Thank you Georgi. That fixed the problem. I wonder how many of the other 
problems I have been have are due to debconf being screwed up. What 
tipped you off? This is not an obvious cause.


Thanks

Gary R.

On 7/3/21 4:39 PM, Georgi Naplatanov wrote:

On 7/4/21 2:17 AM, Gary L. Roach wrote:

Hi all,

Operating System: Debian GNU/Linux 10
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-17-amd64
OS Type: 64-bit
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 15.6 GiB of RAM

I have been trying to get a working installation of Docker. This should
be easy considering all of the information available. Alas, for me, this
doesn't seem to be the case. My latest attempt was to use the
instructions at
*https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-debian-10*
. I followed the instructions to the letter with the exception of
skipping over the repository setup that I installed before. I got the
following:


apt install docker-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
   docker-ce-cli docker-ce-rootless-extras docker-scan-plugin
Recommended packages:
   slirp4netns
The following NEW packages will be installed:
   docker-ce docker-ce-cli docker-ce-rootless-extras docker-scan-plugin
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/79.1 MB of archives.
After this operation, 335 MB of additional disk space will be used.
Do you want to continue? [Y/n]
qt.qpa.screen: QXcbConnection: Could not connect to display
/Could not connect to any X display./
debconf: unable to initialize frontend: Kde
debconf: (debconf-kde-helper terminated abnormally (exit status: 1))
debconf: falling back to frontend: Qt
debconf: unable to initialize frontend: Qt
debconf: (Can't locate Debconf/FrontEnd/Qt.pm in @INC (you may need to
install the Debconf::FrontEnd::Qt module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1
/usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28
/usr/share/perl/5.28 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base) at (eval 22) line 2.)
debconf: falling back to frontend: Dialog
Selecting previously unselected package docker-ce-cli.
(Reading database ... 263049 files and directories currently installed.)
Preparing to unpack
.../docker-ce-cli_5%3a20.10.7~3-0~debian-buster_amd64.deb ...
Unpacking docker-ce-cli (5:20.10.7~3-0~debian-buster) ...
Selecting previously unselected package docker-ce.
Preparing to unpack
.../docker-ce_5%3a20.10.7~3-0~debian-buster_amd64.deb ...
Unpacking docker-ce (5:20.10.7~3-0~debian-buster) ...
Selecting previously unselected package docker-ce-rootless-extras.
Preparing to unpack
.../docker-ce-rootless-extras_5%3a20.10.7~3-0~debian-buster_amd64.deb ...
Unpacking docker-ce-rootless-extras (5:20.10.7~3-0~debian-buster) ...
Selecting previously unselected package docker-scan-plugin.
Preparing to unpack
.../docker-scan-plugin_0.8.0~debian-buster_amd64.deb ...
Unpacking docker-scan-plugin (0.8.0~debian-buster) ...
Setting up docker-scan-plugin (0.8.0~debian-buster) ...
Setting up docker-ce-cli (5:20.10.7~3-0~debian-buster) ...
Setting up docker-ce-rootless-extras (5:20.10.7~3-0~debian-buster) ...
Setting up docker-ce (5:20.10.7~3-0~debian-buster) ...Could not
connect to any X display.
Created symlink
/etc/systemd/system/multi-user.target.wants/docker.service →
/lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket
→ /lib/systemd/system/docker.socket.
Job for docker.service failed because the control process exited with
error code.
See "systemctl status docker.service" and "journalctl -xe" for
details.Could not connect to any X display.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
    Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor
preset: enabled)
    Active: activating (auto-restart) (Result: exit-code) since Sat
2021-07-03 15:54:00 PDT; 9ms ago
  Docs: https://docs.docker.com
   Process: 28141 ExecStart=/usr/bin/dockerd -H fd://
--containerd=/run/containerd/containerd.sock (code=exited,
status=1/FAILURE)
  Main PID: 28141 (code=exited, status=1/FAILURE)
dpkg: error processing package docker-ce (--configure):
  installed docker-ce package post-installation script subprocess
returned error exit status 1
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (241-7~deb10u7) ...
Errors were encountered while processing:
  docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:/var/run/docker#

Re: Docker installation problem

[Georgi Naplatanov]

On 7/4/21 2:17 AM, Gary L. Roach wrote:
> Hi all,
> 
> Operating System: Debian GNU/Linux 10
> KDE Plasma Version: 5.14.5
> Qt Version: 5.11.3
> KDE Frameworks Version: 5.54.0
> Kernel Version: 4.19.0-17-amd64
> OS Type: 64-bit
> Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
> Memory: 15.6 GiB of RAM
> 
> I have been trying to get a working installation of Docker. This should
> be easy considering all of the information available. Alas, for me, this
> doesn't seem to be the case. My latest attempt was to use the
> instructions at
> *https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-debian-10*
> . I followed the instructions to the letter with the exception of
> skipping over the repository setup that I installed before. I got the
> following:
> 
>> apt install docker-ce
>> Reading package lists... Done
>> Building dependency tree   
>> Reading state information... Done
>> The following additional packages will be installed:
>>   docker-ce-cli docker-ce-rootless-extras docker-scan-plugin
>> Recommended packages:
>>   slirp4netns
>> The following NEW packages will be installed:
>>   docker-ce docker-ce-cli docker-ce-rootless-extras docker-scan-plugin
>> 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
>> Need to get 0 B/79.1 MB of archives.
>> After this operation, 335 MB of additional disk space will be used.
>> Do you want to continue? [Y/n]
>> qt.qpa.screen: QXcbConnection: Could not connect to display
>> /Could not connect to any X display./
>> debconf: unable to initialize frontend: Kde
>> debconf: (debconf-kde-helper terminated abnormally (exit status: 1))
>> debconf: falling back to frontend: Qt
>> debconf: unable to initialize frontend: Qt
>> debconf: (Can't locate Debconf/FrontEnd/Qt.pm in @INC (you may need to
>> install the Debconf::FrontEnd::Qt module) (@INC contains: /etc/perl
>> /usr/local/lib/x86_64-linux-gnu/perl/5.28.1
>> /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28
>> /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28
>> /usr/share/perl/5.28 /usr/local/lib/site_perl
>> /usr/lib/x86_64-linux-gnu/perl-base) at (eval 22) line 2.)
>> debconf: falling back to frontend: Dialog
>> Selecting previously unselected package docker-ce-cli.
>> (Reading database ... 263049 files and directories currently installed.)
>> Preparing to unpack
>> .../docker-ce-cli_5%3a20.10.7~3-0~debian-buster_amd64.deb ...
>> Unpacking docker-ce-cli (5:20.10.7~3-0~debian-buster) ...
>> Selecting previously unselected package docker-ce.
>> Preparing to unpack
>> .../docker-ce_5%3a20.10.7~3-0~debian-buster_amd64.deb ...
>> Unpacking docker-ce (5:20.10.7~3-0~debian-buster) ...
>> Selecting previously unselected package docker-ce-rootless-extras.
>> Preparing to unpack
>> .../docker-ce-rootless-extras_5%3a20.10.7~3-0~debian-buster_amd64.deb ...
>> Unpacking docker-ce-rootless-extras (5:20.10.7~3-0~debian-buster) ...
>> Selecting previously unselected package docker-scan-plugin.
>> Preparing to unpack
>> .../docker-scan-plugin_0.8.0~debian-buster_amd64.deb ...
>> Unpacking docker-scan-plugin (0.8.0~debian-buster) ...
>> Setting up docker-scan-plugin (0.8.0~debian-buster) ...
>> Setting up docker-ce-cli (5:20.10.7~3-0~debian-buster) ...
>> Setting up docker-ce-rootless-extras (5:20.10.7~3-0~debian-buster) ...
>> Setting up docker-ce (5:20.10.7~3-0~debian-buster) ...Could not
>> connect to any X display.
>> Created symlink
>> /etc/systemd/system/multi-user.target.wants/docker.service →
>> /lib/systemd/system/docker.service.
>> Created symlink /etc/systemd/system/sockets.target.wants/docker.socket
>> → /lib/systemd/system/docker.socket.
>> Job for docker.service failed because the control process exited with
>> error code.
>> See "systemctl status docker.service" and "journalctl -xe" for
>> details.Could not connect to any X display.
>> invoke-rc.d: initscript docker, action "start" failed.
>> ● docker.service - Docker Application Container Engine
>>    Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor
>> preset: enabled)
>>    Active: activating (auto-restart) (Result: exit-code) since Sat
>> 2021-07-03 15:54:00 PDT; 9ms ago
>>  Docs: https://docs.docker.com
>>   Process: 28141 ExecStart=/usr/bin/dockerd -H fd://
>> --containerd=/run/containerd/containerd.sock (code=exited,
>> status=1/FAILURE)
>>  Main PID: 28141 (code=exited, status=1/FAILURE)
>> dpkg: error processing package docker-ce (--configure):
>>  installed docker-ce package post-installation script subprocess
>> returned error exit status 1
>> Processing triggers for man-db (2.8.5-2) ...
>> Processing triggers for systemd (241-7~deb10u7) ...
>> Errors were encountered while processing:
>>  docker-ce
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>> root@debian:/var/run/docker#
>> 

Docker installation problem

[Gary L. Roach]

Hi all,

Operating System: Debian GNU/Linux 10
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-17-amd64
OS Type: 64-bit
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 15.6 GiB of RAM

I have been trying to get a working installation of Docker. This should 
be easy considering all of the information available. Alas, for me, this 
doesn't seem to be the case. My latest attempt was to use the 
instructions at 
*https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-debian-10* 
. I followed the instructions to the letter with the exception of 
skipping over the repository setup that I installed before. I got the 
following:



apt install docker-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  docker-ce-cli docker-ce-rootless-extras docker-scan-plugin
Recommended packages:
  slirp4netns
The following NEW packages will be installed:
  docker-ce docker-ce-cli docker-ce-rootless-extras docker-scan-plugin
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/79.1 MB of archives.
After this operation, 335 MB of additional disk space will be used.
Do you want to continue? [Y/n]
qt.qpa.screen: QXcbConnection: Could not connect to display
/Could not connect to any X display./
debconf: unable to initialize frontend: Kde
debconf: (debconf-kde-helper terminated abnormally (exit status: 1))
debconf: falling back to frontend: Qt
debconf: unable to initialize frontend: Qt
debconf: (Can't locate Debconf/FrontEnd/Qt.pm in @INC (you may need to 
install the Debconf::FrontEnd::Qt module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 
/usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 
/usr/share/perl/5.28 /usr/local/lib/site_perl 
/usr/lib/x86_64-linux-gnu/perl-base) at (eval 22) line 2.)

debconf: falling back to frontend: Dialog
Selecting previously unselected package docker-ce-cli.
(Reading database ... 263049 files and directories currently installed.)
Preparing to unpack 
.../docker-ce-cli_5%3a20.10.7~3-0~debian-buster_amd64.deb ...

Unpacking docker-ce-cli (5:20.10.7~3-0~debian-buster) ...
Selecting previously unselected package docker-ce.
Preparing to unpack 
.../docker-ce_5%3a20.10.7~3-0~debian-buster_amd64.deb ...

Unpacking docker-ce (5:20.10.7~3-0~debian-buster) ...
Selecting previously unselected package docker-ce-rootless-extras.
Preparing to unpack 
.../docker-ce-rootless-extras_5%3a20.10.7~3-0~debian-buster_amd64.deb ...

Unpacking docker-ce-rootless-extras (5:20.10.7~3-0~debian-buster) ...
Selecting previously unselected package docker-scan-plugin.
Preparing to unpack 
.../docker-scan-plugin_0.8.0~debian-buster_amd64.deb ...

Unpacking docker-scan-plugin (0.8.0~debian-buster) ...
Setting up docker-scan-plugin (0.8.0~debian-buster) ...
Setting up docker-ce-cli (5:20.10.7~3-0~debian-buster) ...
Setting up docker-ce-rootless-extras (5:20.10.7~3-0~debian-buster) ...
Setting up docker-ce (5:20.10.7~3-0~debian-buster) ...Could not 
connect to any X display.
Created symlink 
/etc/systemd/system/multi-user.target.wants/docker.service → 
/lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket 
→ /lib/systemd/system/docker.socket.
Job for docker.service failed because the control process exited with 
error code.
See "systemctl status docker.service" and "journalctl -xe" for 
details.Could not connect to any X display.

invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor 
preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sat 
2021-07-03 15:54:00 PDT; 9ms ago

 Docs: https://docs.docker.com
  Process: 28141 ExecStart=/usr/bin/dockerd -H fd:// 
--containerd=/run/containerd/containerd.sock (code=exited, 
status=1/FAILURE)

 Main PID: 28141 (code=exited, status=1/FAILURE)
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess 
returned error exit status 1

Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (241-7~deb10u7) ...
Errors were encountered while processing:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:/var/run/docker# 
https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-debian-10https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-debian-10https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-debian-10https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-debian-10
Note the error at docker.service and the /"Could not connect to any X 
display" problem/. I'm not sure 

Re: Installation problem

[Dan Ritter]

David Christensen wrote: 
> On 2/28/21 2:12 PM, Alan Glasser wrote:
> > I am trying to install Buster on an old 386.
> 
> I do not believe the Intel 80386 processor is supported by Linux any more:
> 
> https://www.phoronix.com/scan.php?page=news_item=MTI0OTg

Good catch.

$50 in Raspberry Pi parts is literally much faster than any 386
ever made. The $100 Raspberry Pi 400 kit is everything needed
for a desktop system except for a monitor.

-dsr-

Re: Installation problem

[Darac Marjal]

On 28/02/2021 22:12, Alan Glasser wrote:
> I am trying to install Buster on an old 386.
> I burned the three full DVDs.
> I boot the first DVD and it gets to the point of asking about
> additional cds/dvds.
> I push the eject button on my dvd drive and nothing happens.  I try to
> do a forced eject
> with a paperclip, but that doesn't work either.  I click "No" as I
> can't eject the DVD.
> Nothing happens.
>
> This is repeatable on my machine.
> Three times; same behavior.
>
> Any ideas?

Try switching to a Console (Left Alt + F4) and running the command
"eject". Operating systems have the ability to "lock" optical drives so
that you don't, say, eject a drive that's being written to. The
Installer should, clearly, be unlocking the drive at this point if it
expects you to swap disks, but either you're not at the right point in
the installer (might you, for example, be on an explanation page, and
the NEXT page is where the drive unlocks?) or there's a bug. Either way,
'eject' should at the very least give you an error message you can work
with.


>
> Thanks for your help.
>
> Alan Glasser
>



OpenPGP_signature
Description: OpenPGP digital signature

Re: Installation problem

[David Christensen]

On 2/28/21 2:12 PM, Alan Glasser wrote:

I am trying to install Buster on an old 386.
I burned the three full DVDs.
I boot the first DVD and it gets to the point of asking about additional
cds/dvds.
I push the eject button on my dvd drive and nothing happens.  I try to do a
forced eject
with a paperclip, but that doesn't work either.  I click "No" as I can't
eject the DVD.
Nothing happens.

This is repeatable on my machine.
Three times; same behavior.

Any ideas?

Thanks for your help.


I do not believe the Intel 80386 processor is supported by Linux any more:

https://www.phoronix.com/scan.php?page=news_item=MTI0OTg


David

Re: Installation problem

[Dan Ritter]

Alan Glasser wrote: 
> I am trying to install Buster on an old 386.
> I burned the three full DVDs.
> I boot the first DVD and it gets to the point of asking about additional
> cds/dvds.

You don't need them at this point. You can add them later.

-dsr-

Installation problem

[Alan Glasser]

I am trying to install Buster on an old 386.
I burned the three full DVDs.
I boot the first DVD and it gets to the point of asking about additional
cds/dvds.
I push the eject button on my dvd drive and nothing happens.  I try to do a
forced eject
with a paperclip, but that doesn't work either.  I click "No" as I can't
eject the DVD.
Nothing happens.

This is repeatable on my machine.
Three times; same behavior.

Any ideas?

Thanks for your help.

Alan Glasser

Re: Installation Problem

[Andrei POPESCU]

On Mi, 15 iul 20, 18:07:53, Vlad Dragomir wrote:
> Worked like a charm, I'm almost at the end of the installation process.
> 
> Yes indeed, the downloaded archive contains more firmware compared to the 
> installation disc, not very logical in my opinion but I am not a pro.
> 
> Thank you so much, virtual pints for everybody!

Hi Vlad,

This sounds like a problem with either the installer or the way the 
image was built.

Please file an "installation-report" after you are finished with

reportbug installation-report

Have fun with Debian,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

RE: Installation Problem

[Vlad Dragomir]

Worked like a charm, I'm almost at the end of the installation process.

Yes indeed, the downloaded archive contains more firmware compared to the 
installation disc, not very logical in my opinion but I am not a pro.

Thank you so much, virtual pints for everybody!

Cheers,

Vlad.

Re: Installation Problem

[Dan Ritter]

Vlad Dragomir wrote: 
> Hello,
> 
> Thank you all for all those great responses, I'm definitely grateful.
> 
> Dan, I followed your instructions, please tell me if this is the expected 
> output, I'll try to transcribe everything:
> Network controller: Intel Corporation Wireless 8260 (rev 3a)
> 
> Would you please tell me what to do next?

Good news. This adapter is well-supported. It does need a
non-free firmware blob, which is packaged as firmware-iwlwifi.

The curious thing is, the install disc that you downloaded
should have that package.

Anyway. Grab
http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/buster/current/

and uncompress one of those three archives on a USB stick; when
the installer asks you if you have a removable disk with drivers
or firmware, plug it in.

Around the middle of the install, the installer will ask you
what Debian repositories to enable. In addition to selecting
security updates, add non-free. 

-dsr-

Re: Installation Problem

[Richard Owlett]

On 07/14/2020 03:33 PM, Vlad Dragomir wrote:

Good evening,

I am very new to Debian, and would like to apologise first, I might not know 
how exactly to describe this issue.

I tried to install Debian on an unused laptop I'm having, [ *SNIP* ]


What is make and model of the laptop?

Re: Installation Problem

[tomas]

On Tue, Jul 14, 2020 at 11:14:16PM -0500, David Wright wrote:
> On Wed 15 Jul 2020 at 05:43:06 (+0200), Vlad Dragomir wrote:
> > 
> > I found that file too, actually I found four or five of them, but not all. 
> > I put them on the USB installation drive but the installer kept asking for 
> > them. I'm sorry, I should have been more precise when I said that Google 
> > didn't help me much. What I meant was: it only found a few of those files 
> > and they were ignored by the installer.
> 
> The most reliable place I've found in the past was in the top-level
> directory on an ordinary FAT-partitioned USB stick.
> 
> The installer writes a log to VC4, which should record where it
 

This is "virtual console 4". You switch to it by hitting CTRL-ALT-F4.
Similarly...

> looks. If the lines in question have already scrolled off the screen,
> the log can be displayed (rather tediously) with the command
> # more /var/log/syslog
> in a shell you can open on VC2 or VC3.

...for the other virtual consoles.

Cheers
-- t


signature.asc
Description: Digital signature

Re: Installation Problem

[David Wright]

On Wed 15 Jul 2020 at 05:43:06 (+0200), Vlad Dragomir wrote:
> 
> I found that file too, actually I found four or five of them, but not all. I 
> put them on the USB installation drive but the installer kept asking for 
> them. I'm sorry, I should have been more precise when I said that Google 
> didn't help me much. What I meant was: it only found a few of those files and 
> they were ignored by the installer.

The most reliable place I've found in the past was in the top-level
directory on an ordinary FAT-partitioned USB stick.

The installer writes a log to VC4, which should record where it
looks. If the lines in question have already scrolled off the screen,
the log can be displayed (rather tediously) with the command
# more /var/log/syslog
in a shell you can open on VC2 or VC3.

Cheers,
David.

RE: Installation Problem

[Vlad Dragomir]

Hello,

Thank you all for all those great responses, I'm definitely grateful.

Dan, I followed your instructions, please tell me if this is the expected 
output, I'll try to transcribe everything:
Network controller: Intel Corporation Wireless 8260 (rev 3a)

Would you please tell me what to do next?

David,

I found that file too, actually I found four or five of them, but not all. I 
put them on the USB installation drive but the installer kept asking for them. 
I'm sorry, I should have been more precise when I said that Google didn't help 
me much. What I meant was: it only found a few of those files and they were 
ignored by the installer.

Digital thanks to all those who took a moment to write back!

Vlad. 

Re: Installation Problem

[Bob McGowan]

On 7/14/20 1:48 PM, David Christensen wrote:

On 2020-07-14 13:33, Vlad Dragomir wrote:


I tried to install Debian on an unused laptop I'm having,


It asks for additional non-free firmware, unfortunately it's an Intel 
wireless card. It gives a list of files it needs in order to configure 
the network, which is I suppose a good start. Still,
1.    I have no idea where to find those files, Google didn’t help me 
much with this.
2.    If I find those files, I don’t know where exactly to paste them 
on the installation drive for it to see them.
3.    This installation iso pretends it contains non-free firmware 
already, so normally it shouldn’t ask for those files. Am I missing 
something?
Therefore, I had to cancel the installation, at least for the time 
being. It would be rather useless to have a system without Internet 
access.


Proprietary Wi-Fi firmware is an unending PITA with FOSS.


I buy laptops with wired Ethernet interfaces to avoid this problem.  I 
then use the wired connection for installation and for installing Wi-Fi 
firmware.



If I needed to install Debian on a laptop without Ethernet, I would buy 
a USB Ethernet adapter.  The key is finding one that is supported by 
FOSS OOTB.  Unfortunately, I do not own one and cannot make a 
recommendation.  (And, these products constantly change.)  I would  STFW 
for mailing list and forum archives for USB WiFi adapaters that are 
known to work with Debian 10.  If you are willing to buy used equipment 
(if only to do the install and firmware for the build-in Wi-Fi), eBay is 
a good source.



David

If you need a USB<->Ethernet dongle, I recently purchased one, through 
Amazon.  It is a Gigabit/USB3.0 dongle that works nicely with Debian.


The manufacturer is "plugable" (plugable.com) and the device is model 
USB3-E1000.


As an aside, for anyone that might be interested, I tested it 
successfully with both a Samsung Galaxy S9 cellphone and a Lenovo Tablet 
TB-8504F, which surprised me a bit.  I've also tested on two other 
Android tablets, where it did not work, so mileage will vary.


Regardless, it works with Debian without a hitch. ;)

Bob

Re: Installation Problem

[David Wright]

On Tue 14 Jul 2020 at 16:59:00 (-0400), Dan Ritter wrote:
> Vlad Dragomir wrote: 
> > I am very new to Debian, and would like to apologise first, I might not 
> > know how exactly to describe this issue.
> 
> Everybody starts somewhere.
> 
> 
> > I tried to install Debian on an unused laptop I'm having, using the iso 
> > downloaded from this torrent:
> > https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/10.4.0+nonfree/amd64/bt-dvd/firmware-10.4.0-amd64-DVD-1.iso.torrent
> 
> Pretty good choice.
> 
> > It started wonderfully, the installation went smoothly until it tried to 
> > connect to the Internet. It asks for additional non-free firmware, 
> > unfortunately it's an Intel wireless card. It gives a list of files it 
> > needs in order to configure the network, which is I suppose a good start. 
> > Still,
> > 1.  I have no idea where to find those files, Google didn???t help me much 
> > with this.
> > 2.  If I find those files, I don???t know where exactly to paste them on 
> > the installation drive for it to see them.
> > 3.  This installation iso pretends it contains non-free firmware already, 
> > so normally it shouldn???t ask for those files. Am I missing something?
> > Therefore, I had to cancel the installation, at least for the time being. 
> > It would be rather useless to have a system without Internet access. 
> 
> Let's find out which Intel wireless card you have. With the
> installer running, choose "start local shell".
> 
> Then type 
> 
> lspci 
> 
> and look for lines with Network in them. They should start with
> a number like 03.00 or something like that.
> 
> Tell us the output from
> 
> lspci -vv 
> 
> where  is the number from the Network line.

It seems odd that it's asking for such a long list of files.
I assume it would be happy with just one of them, and it's
just giving alternatives in order of preference.

iwlwifi-8000C-36.ucode
iwlwifi-8000C-35.ucode
iwlwifi-8000C-34.ucode
iwlwifi-8000C-33.ucode
iwlwifi-8000C-32.ucode
iwlwifi-8000C-31.ucode
iwlwifi-8000C-30.ucode
iwlwifi-8000C-29.ucode
iwlwifi-8000C-28.ucode
iwlwifi-8000C-27.ucode
iwlwifi-8000C-26.ucode
iwlwifi-8000C-25.ucode
iwlwifi-8000C-24.ucode
iwlwifi-8000C-23.ucode
iwlwifi-8000C-22.ucode

But even my netinst ISO (firmware-10.2.0-amd64-netinst.iso 394265k Nov 16  2019)
contains the first and last of these:
iwlwifi-8000C-22.ucode 2120860 Aug 22  2019
iwlwifi-8000C-36.ucode 2486572 Aug 22  2019

BTW googling the filename gave me a link to
https://github.com/wkennington/linux-firmware/blob/master/iwlwifi-8000C-36.ucode
as the second hit.

Cheers,
David.

Re: Installation Problem

[Dan Ritter]

Vlad Dragomir wrote: 
> I am very new to Debian, and would like to apologise first, I might not know 
> how exactly to describe this issue.

Everybody starts somewhere.


> I tried to install Debian on an unused laptop I'm having, using the iso 
> downloaded from this torrent:
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/10.4.0+nonfree/amd64/bt-dvd/firmware-10.4.0-amd64-DVD-1.iso.torrent

Pretty good choice.

> It started wonderfully, the installation went smoothly until it tried to 
> connect to the Internet. It asks for additional non-free firmware, 
> unfortunately it's an Intel wireless card. It gives a list of files it needs 
> in order to configure the network, which is I suppose a good start. Still,
> 1.I have no idea where to find those files, Google didn???t help me much 
> with this.
> 2.If I find those files, I don???t know where exactly to paste them on 
> the installation drive for it to see them.
> 3.This installation iso pretends it contains non-free firmware already, 
> so normally it shouldn???t ask for those files. Am I missing something?
> Therefore, I had to cancel the installation, at least for the time being. It 
> would be rather useless to have a system without Internet access. 

Let's find out which Intel wireless card you have. With the
installer running, choose "start local shell".

Then type 

lspci 

and look for lines with Network in them. They should start with
a number like 03.00 or something like that.

Tell us the output from

lspci -vv 

where  is the number from the Network line.

-dsr-

Re: Installation Problem

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



‐‐‐ Original Message ‐‐‐
On Tuesday, July 14, 2020 2:48 PM, David Christensen 
 wrote:

> If I needed to install Debian on a laptop without Ethernet, I would buy
> a USB Ethernet adapter. The key is finding one that is supported by
> FOSS OOTB.

Take a look at Raspberry Pi sources. RPIs have Enet OOTB, but there are lots of 
USB dongles that work with the Debian software in RPIs. Might give a hint. Or 
maybe even a promise.

--
Glenn English

-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJfDhx1AAoJEJ/XhjGCrIwyg/IIAKiLglMRRvbllGSAf3c+
r+qIIGNALyAzlL3gznEeajagdWWubJDV8bRdiOsyl2pYu8FzcQVMz0pzLPUn
irSg5xSg/JRJiNnTpgGXSkJIDgWWV75YiycBza2qBUFclRJUNpbPCeZ+rRQO
PmX/buoJzwgiraWnU882i8edRqOANRfKwQdmFRzXtqFqVJfD2SucLO72858L
SRdsHts2Az4qJkzE/iGEbHI2RdkLe9OgWEiOAzy6Rs81UrOeqc2+VvG/VM+m
oAfoQypBcp+MCgwFfVDdbKNoIbfkKZyIH6aPdXzDY9YPOFt8dTO7+aJa7kjm
In07SN5UKa9JKpgLhZFQ7g0=
=1tkw
-END PGP SIGNATURE-

Re: Installation Problem

[David Christensen]

On 2020-07-14 13:33, Vlad Dragomir wrote:


I tried to install Debian on an unused laptop I'm having,



It asks for additional non-free firmware, unfortunately it's an Intel wireless 
card. It gives a list of files it needs in order to configure the network, 
which is I suppose a good start. Still,
1.  I have no idea where to find those files, Google didn’t help me much 
with this.
2.  If I find those files, I don’t know where exactly to paste them on the 
installation drive for it to see them.
3.  This installation iso pretends it contains non-free firmware already, 
so normally it shouldn’t ask for those files. Am I missing something?
Therefore, I had to cancel the installation, at least for the time being. It 
would be rather useless to have a system without Internet access.


Proprietary Wi-Fi firmware is an unending PITA with FOSS.


I buy laptops with wired Ethernet interfaces to avoid this problem.  I 
then use the wired connection for installation and for installing Wi-Fi 
firmware.



If I needed to install Debian on a laptop without Ethernet, I would buy 
a USB Ethernet adapter.  The key is finding one that is supported by 
FOSS OOTB.  Unfortunately, I do not own one and cannot make a 
recommendation.  (And, these products constantly change.)  I would  STFW 
for mailing list and forum archives for USB WiFi adapaters that are 
known to work with Debian 10.  If you are willing to buy used equipment 
(if only to do the install and firmware for the build-in Wi-Fi), eBay is 
a good source.



David

Installation Problem

[Vlad Dragomir]

Good evening,

I am very new to Debian, and would like to apologise first, I might not know 
how exactly to describe this issue.

I tried to install Debian on an unused laptop I'm having, using the iso 
downloaded from this torrent:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/10.4.0+nonfree/amd64/bt-dvd/firmware-10.4.0-amd64-DVD-1.iso.torrent

It started wonderfully, the installation went smoothly until it tried to 
connect to the Internet. It asks for additional non-free firmware, 
unfortunately it's an Intel wireless card. It gives a list of files it needs in 
order to configure the network, which is I suppose a good start. Still,
1.  I have no idea where to find those files, Google didn’t help me much 
with this.
2.  If I find those files, I don’t know where exactly to paste them on the 
installation drive for it to see them.
3.  This installation iso pretends it contains non-free firmware already, 
so normally it shouldn’t ask for those files. Am I missing something?
Therefore, I had to cancel the installation, at least for the time being. It 
would be rather useless to have a system without Internet access. 

Here is the list of files the installer asks for:
iwlwifi-8000C-36.ucode
iwlwifi-8000C-35.ucode
iwlwifi-8000C-34.ucode
iwlwifi-8000C-33.ucode
iwlwifi-8000C-32.ucode
iwlwifi-8000C-31.ucode
iwlwifi-8000C-30.ucode
iwlwifi-8000C-29.ucode
iwlwifi-8000C-28.ucode
iwlwifi-8000C-27.ucode
iwlwifi-8000C-26.ucode
iwlwifi-8000C-25.ucode
iwlwifi-8000C-24.ucode
iwlwifi-8000C-23.ucode
iwlwifi-8000C-22.ucode

I will be grateful for any tip that would help me make this work, I'm not ready 
to give up, would love to keep one foot in the world of free software, except 
for the Network card of course. *smile*

Thanks for helping the newbie, and sorry again if I'm not asking things the 
right way.

Regards,

Vlad.

Re: Installation problem

[Felix Miata]

Thomas D Dial composed on 2019-09-14 13:30 (UTC-0600):

> As a first "next step" I suggest the following:

> When you see the "Debian page" - that is the Grub boot menu - press the
> 'e' key. This will present the boot control instructions for the default
> boot into your Linux in a form you can edit using the arrow keys to move
> the cursor, backspace to erase, and normal keys to add things.

> Locate the line beginning "linux." This probably has the word "quiet" at
> or near the end, which prevents display of normal boot messages that do
> not report serious problems; erase it and press control-x or the F10 key
> to continue the boot.

> You should see messages as the system boots and initializes Linux. The
> last of them are likely to provide information about the reason the
> system initialization does not complete. They may be self explanatory,
> but if not, you can post them here and they may help others to provide
> additional assistance.

As a second step, if above seems minimally or un- helpful, after removing quiet,
append a space, then the string

nomodeset

which is primarily a troubleshooting parameter, also for enabling repairs,
explained among other places at:

-- 
Evolution as taught in public schools is religion, not science.

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

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

Re: Installation problem

[Thomas D Dial]

On Sat, 2019-09-14 at 08:46 +0200, john doe wrote:
> On 9/14/2019 7:36 AM, David Christensen wrote:
> > On 9/13/19 4:45 PM, Anne wrote:
> > > Hi, I am new to debian and I can not seem to get the OS installed
> > > properly.
> > > 
> > > What I have done so far is to
> > > 
> > > Make a free space partition of 100GB on drive D and then
> > > 
> > > 1. download the first DVD of 10.1.0
> > > 2. used rufus to put it on a thumb drive
> > > 3. Booted from the thumb drive and selected "graphical Install"
> > > 4. followed the prompts
> > > 5. Program said OS was installed and to reboot the system
> > > 6. reboot
> > > 7. Debian page showed up and I selected the first selection.
> > > 8. after a bit of doing things I get a black screen with a small
> > > cursor in the upper left of the screen
> > > 9. a power off or ctrl alt del is required to go further.
> > > 10. after reboot I get the Debian screen and select windows and I
> > > am
> > > up and running again.
> > > 
> > > I have done this three times
> > > 
> > > Twice with the DVD debian-10.1.0-amd64-DVD-1.iso
> > > and once with the DVD firmware-10.1.0-amd64-DVD-1.iso
> > > 
> > > results were the same each time...
> > > 
> > > What am I doing wrong???
> > 
> > You are headed down the path of "dual boot", which is unnecessarily
> > difficult and risks damaging your Windows installation.
> > 
> > 
> > If you have a Windows computer and you want to experiment with GNU/
> > Linux , you are better off installing virtual machine hosting
> > software
> > and downloading a pre-built virtual machine.  Obvious choices
> > include
> > Microsoft Hyper-V, Oracle VirtualBox, and VMware Workstation Player:
> > 
> > https://docs.microsoft.com/en-us/virtualization/
> > 
> > https://www.virtualbox.org/
> > 
> > https://www.vmware.com/
> > 
> 
> https://qemu.org
> 
> Given that you didn't crash your system with multiboot and that you
> see
> the prompt to select which OS to choose, I would keep the multiboot
> going.
> 
> Have you turned off fastboot on windows?
> 
> You shouldn't see D on Windows but somespace that Windows can't use.

Welcome to Debian. I suspect your installation, from either of the
sources you mention, is salvageable. And I think the advice here from
john doe is a good continuation point; it appears you have succeeded in
building a very nearly successful Windows/Linux dual boot setup.

As a first "next step" I suggest the following:

When you see the "Debian page" - that is the Grub boot menu - press the
'e' key. This will present the boot control instructions for the default
boot into your Linux in a form you can edit using the arrow keys to move
the cursor, backspace to erase, and normal keys to add things.

Locate the line beginning "linux." This probably has the word "quiet" at
or near the end, which prevents display of normal boot messages that do
not report serious problems; erase it and press control-x or the F10 key
to continue the boot.

You should see messages as the system boots and initializes Linux. The
last of them are likely to provide information about the reason the
system initialization does not complete. They may be self explanatory,
but if not, you can post them here and they may help others to provide
additional assistance.

Regards,
Tom Dial
 
> 
> --
> John Doe

Re: Installation problem

[Esteban L]

What Video card do you have?

I experienced annoyance with AMD video card/driver. If that is the case,
you can search on google, or ask the mailling list again for how to
install the required firmware.

Unfortunately, it is not smooth.

On 14.09.19 01:45, Anne wrote:
>
> Hi, I am new to debian and I can not seem to get the OS installed
> properly.
>
> What I have done so far is to
>
> Make a free space partition of 100GB on drive D and then
>
> 1. download the first DVD of 10.1.0
> 2. used rufus to put it on a thumb drive
> 3. Booted from the thumb drive and selected "graphical Install"
> 4. followed the prompts
> 5. Program said OS was installed and to reboot the system
> 6. reboot
> 7. Debian page showed up and I selected the first selection.
> 8. after a bit of doing things I get a black screen with a small
> cursor in the upper left of the screen
> 9. a power off or ctrl alt del is required to go further.
> 10. after reboot I get the Debian screen and select windows and I am
> up and running again.
>
> I have done this three times
>
> Twice with the DVD  debian-10.1.0-amd64-DVD-1.iso
> and once with the DVD firmware-10.1.0-amd64-DVD-1.iso
>
> results were the same each time...
>
> What am I doing wrong???
>
> Anne
>

Re: Installation problem

[Joe]

On Fri, 13 Sep 2019 22:36:06 -0700
David Christensen  wrote:

> On 9/13/19 4:45 PM, Anne wrote:
> > Hi, I am new to debian and I can not seem to get the OS installed
> > properly.
> > 
> > What I have done so far is to
> > 
> > Make a free space partition of 100GB on drive D and then
> > 
> > 1. download the first DVD of 10.1.0
> > 2. used rufus to put it on a thumb drive
> > 3. Booted from the thumb drive and selected "graphical Install"
> > 4. followed the prompts
> > 5. Program said OS was installed and to reboot the system
> > 6. reboot
> > 7. Debian page showed up and I selected the first selection.
> > 8. after a bit of doing things I get a black screen with a small
> > cursor in the upper left of the screen
> > 9. a power off or ctrl alt del is required to go further.
> > 10. after reboot I get the Debian screen and select windows and I
> > am up and running again.
> > 
> > I have done this three times
> > 
> > Twice with the DVD debian-10.1.0-amd64-DVD-1.iso
> > and once with the DVD firmware-10.1.0-amd64-DVD-1.iso
> > 
> > results were the same each time...
> > 
> > What am I doing wrong???  
> 
> You are headed down the path of "dual boot", which is unnecessarily 
> difficult and risks damaging your Windows installation.
> 

Doesn't have to be. I bought a Win10 netbook last year, with no legacy
BIOS option, and stretch installed on it on a second drive without a
problem. I hadn't actually intended to use it dual-boot, but I found
that the grub menu contained a Windows entry, and it worked easily.

> 
> If you have a Windows computer and you want to experiment with GNU/ 
> Linux , you are better off installing virtual machine hosting
> software and downloading a pre-built virtual machine.  Obvious
> choices include Microsoft Hyper-V, Oracle VirtualBox, and VMware
> Workstation Player:
> 
> https://docs.microsoft.com/en-us/virtualization/
> 
> https://www.virtualbox.org/
> 
> https://www.vmware.com/

What I'd suggest first is trying a live version of Debian, perhaps
Knoppix https://www.knopper.net/knoppix/index-en.html and preferably
also straight Debian, to see if there are any hardware issues. Doing a
graphical install does not guarantee that the graphics drivers in the
installed Debian will work, I've had trouble in that area.

-- 
Joe

Re: Installation problem

[john doe]

On 9/14/2019 7:36 AM, David Christensen wrote:
> On 9/13/19 4:45 PM, Anne wrote:
>> Hi, I am new to debian and I can not seem to get the OS installed
>> properly.
>>
>> What I have done so far is to
>>
>> Make a free space partition of 100GB on drive D and then
>>
>> 1. download the first DVD of 10.1.0
>> 2. used rufus to put it on a thumb drive
>> 3. Booted from the thumb drive and selected "graphical Install"
>> 4. followed the prompts
>> 5. Program said OS was installed and to reboot the system
>> 6. reboot
>> 7. Debian page showed up and I selected the first selection.
>> 8. after a bit of doing things I get a black screen with a small
>> cursor in the upper left of the screen
>> 9. a power off or ctrl alt del is required to go further.
>> 10. after reboot I get the Debian screen and select windows and I am
>> up and running again.
>>
>> I have done this three times
>>
>> Twice with the DVD debian-10.1.0-amd64-DVD-1.iso
>> and once with the DVD firmware-10.1.0-amd64-DVD-1.iso
>>
>> results were the same each time...
>>
>> What am I doing wrong???
>
> You are headed down the path of "dual boot", which is unnecessarily
> difficult and risks damaging your Windows installation.
>
>
> If you have a Windows computer and you want to experiment with GNU/
> Linux , you are better off installing virtual machine hosting software
> and downloading a pre-built virtual machine.  Obvious choices include
> Microsoft Hyper-V, Oracle VirtualBox, and VMware Workstation Player:
>
> https://docs.microsoft.com/en-us/virtualization/
>
> https://www.virtualbox.org/
>
> https://www.vmware.com/
>

https://qemu.org

Given that you didn't crash your system with multiboot and that you see
the prompt to select which OS to choose, I would keep the multiboot going.

Have you turned off fastboot on windows?

You shouldn't see D on Windows but somespace that Windows can't use.

--
John Doe

Re: Installation problem

[Joao Emanuel]

Hi, first sorry for horrible english, well try to turn off secure boot in
bios and try again to install Debian. Or like David suggestion, get
virtualbox or enable hyper-v and install in virtual machine.

Em sex, 13 de set de 2019 às 19:54, Anne  escreveu:

> Hi, I am new to debian and I can not seem to get the OS installed properly.
>
> What I have done so far is to
>
> Make a free space partition of 100GB on drive D and then
>
> 1. download the first DVD of 10.1.0
> 2. used rufus to put it on a thumb drive
> 3. Booted from the thumb drive and selected "graphical Install"
> 4. followed the prompts
> 5. Program said OS was installed and to reboot the system
> 6. reboot
> 7. Debian page showed up and I selected the first selection.
> 8. after a bit of doing things I get a black screen with a small cursor in
> the upper left of the screen
> 9. a power off or ctrl alt del is required to go further.
> 10. after reboot I get the Debian screen and select windows and I am up
> and running again.
>
> I have done this three times
>
> Twice with the DVD  debian-10.1.0-amd64-DVD-1.iso
> and once with the DVD firmware-10.1.0-amd64-DVD-1.iso
>
> results were the same each time...
>
> What am I doing wrong???
>
> Anne
>


-- 

Muito obrigado antecipadamente pela atenção prestada a esta mensagem.

--

{}s

Joao Emanuel

Re: Installation problem

[David Christensen]

On 9/13/19 4:45 PM, Anne wrote:

Hi, I am new to debian and I can not seem to get the OS installed properly.

What I have done so far is to

Make a free space partition of 100GB on drive D and then

1. download the first DVD of 10.1.0
2. used rufus to put it on a thumb drive
3. Booted from the thumb drive and selected "graphical Install"
4. followed the prompts
5. Program said OS was installed and to reboot the system
6. reboot
7. Debian page showed up and I selected the first selection.
8. after a bit of doing things I get a black screen with a small cursor 
in the upper left of the screen

9. a power off or ctrl alt del is required to go further.
10. after reboot I get the Debian screen and select windows and I am up 
and running again.


I have done this three times

Twice with the DVD debian-10.1.0-amd64-DVD-1.iso
and once with the DVD firmware-10.1.0-amd64-DVD-1.iso

results were the same each time...

What am I doing wrong???


You are headed down the path of "dual boot", which is unnecessarily 
difficult and risks damaging your Windows installation.



If you have a Windows computer and you want to experiment with GNU/ 
Linux , you are better off installing virtual machine hosting software 
and downloading a pre-built virtual machine.  Obvious choices include 
Microsoft Hyper-V, Oracle VirtualBox, and VMware Workstation Player:


https://docs.microsoft.com/en-us/virtualization/

https://www.virtualbox.org/

https://www.vmware.com/


David

Re: Installation problem

[Kent West]

On Fri, Sep 13, 2019, 6:55 PM Anne  wrote:

Hi, I am new to debian and I can not seem to get the OS installed properly.

What I have done so far is to

Make a free space partition of 100GB on drive D and then

1. download the first DVD of 10.1.0
2. used rufus to put it on a thumb drive
3. Booted from the thumb drive and selected "graphical Install"
4. followed the prompts
5. Program said OS was installed and to reboot the system


During the install, did it repetition your drive, perhaps taking "D" and
reformatting it?

Your reference to "D" makes me think you have a partition that Windows
calls "D:", using an NTFS file system. Debian generally wants an EXT4 file
system, not an NTFS partition. Is drive "D:" missing from Windows after the
install?


-- 
Kent

Installation problem

[Anne]

Hi, I am new to debian and I can not seem to get the OS installed properly.

What I have done so far is to

Make a free space partition of 100GB on drive D and then

1. download the first DVD of 10.1.0
2. used rufus to put it on a thumb drive
3. Booted from the thumb drive and selected "graphical Install"
4. followed the prompts
5. Program said OS was installed and to reboot the system
6. reboot
7. Debian page showed up and I selected the first selection.
8. after a bit of doing things I get a black screen with a small cursor 
in the upper left of the screen

9. a power off or ctrl alt del is required to go further.
10. after reboot I get the Debian screen and select windows and I am up 
and running again.


I have done this three times

Twice with the DVD debian-10.1.0-amd64-DVD-1.iso
and once with the DVD firmware-10.1.0-amd64-DVD-1.iso

results were the same each time...

What am I doing wrong???

Anne

Fwd: installation problem

[Filippo Faldetta]

Hi,



i've got the error message NMI watchdog: BUG: soft lockup - CPU#2 stuck for
23s! [plymouthd:305] on the startup of my system (even live-cd).
My pc is a dell inspiron 7559 with intel graphic and nvidia.
please help me...i don't want to use windows anymore.



Greetings

Filippo Faldetta

installation problem

[filippo.faldetta]

Hi,

i've got the error message NMI watchdog: BUG: soft lockup - CPU#2 stuck for 
23s! [plymouthd:305] on the startup of my system (even live-cd). 
My pc is a dell inspiron 7559 with intel graphic and nvidia.
please help me...i don't want to use windows anymore.

Greetings
Filippo Faldetta

installation problem

[Moreanu Robert - Nicolae]

i looking to resolve this problem when I want to install debian 8.2 or 8.1.
I receive this message after it's take to Grub install

" the 'grub-pc' package failed to install into /target/ "
after the operation of clean up on installing, i have a failed operations.

I don't have such expertise, please make the debian on install with more
information and what procedure to do that for the people don't have the
time to study the debian.

so.. how i could resolve this problem , any help from you, please

robert, waiting for your response

-- 

*o zi frumoasa !Robert - Nicolae  MOREANU*

Re: installation problem

[Patrick Bartek]

On Sun, 17 Jan 2016, Moreanu Robert - Nicolae wrote:

> i looking to resolve this problem when I want to install debian 8.2
> or 8.1. I receive this message after it's take to Grub install
> 
> " the 'grub-pc' package failed to install into /target/ "
> after the operation of clean up on installing, i have a failed
> operations.
> 
> I don't have such expertise, please make the debian on install with
> more information and what procedure to do that for the people don't
> have the time to study the debian.
> 
> so.. how i could resolve this problem , any help from you, please
> 
> robert, waiting for your response

Since you lack "expertise," I suggest you find someone who has the
expertise to come to your computer and do your install.  If you want to
gain "expertise" to do it yourself, the links below should get you
started.

   https://www.debian.org/releases/stable/installmanual
   https://www.debian.org/releases/jessie/

B

Re: installation problem

[Dick Thomas]

On Sunday 17 Jan 2016 14:53:19 Moreanu Robert - Nicolae wrote:
> i looking to resolve this problem when I want to install debian 8.2 or 8.1.
> I receive this message after it's take to Grub install
> 
> " the 'grub-pc' package failed to install into /target/ "
> after the operation of clean up on installing, i have a failed operations.
> 
> I don't have such expertise, please make the debian on install with more
> information and what procedure to do that for the people don't have the
> time to study the debian.
> 
> so.. how i could resolve this problem , any help from you, please
> 
> robert, waiting for your response

1st question, Have you done a custom partitioning ?

I ask as I've only seen this error on my installs when I've done a encrypted 
root on and didn't leave a /boot unencrypted 



regards

Dick Thomas

Re: Installation Problem

[Florian Pelgrim]

Hi,

this list is for Debian and not for Kali itself.

But I will make a guess and say eject the ISO from your (virtual) drive. ;)

Cheers
Flo

Am 28.10.15 um 15:56 schrieb Ssov Samoht:
> Hello,
> 
> Ive recently been trying to install Debian Kali Linux and it takes me a long 
> time to install it but when its done it just goes back to the starting screen 
> and all i can select it
> 
> Install
> Advanced Options
> Help
> Install with speech synthesis
> 
> Please help me ):
> 



signature.asc
Description: OpenPGP digital signature

Installation Problem

[Ssov Samoht]

Hello,

Ive recently been trying to install Debian Kali Linux and it takes me a long 
time to install it but when its done it just goes back to the starting screen 
and all i can select it

Install
Advanced Options
Help
Install with speech synthesis

Please help me ):

Re: Installation Problem

[Darac Marjal]

On Wed, Oct 28, 2015 at 06:56:51PM +0400, Ssov Samoht wrote:


Hello,

Ive recently been trying to install Debian Kali Linux and it takes me 
a long time to install it but when its done it just goes back to the 
starting screen and all i can select it


Install Advanced Options Help Install with speech synthesis

Please help me ):


Hopefully obvious, but have you tried removing/ejecting the installation 
medium during the reboot?



-- For more information, please reread.


signature.asc
Description: PGP signature

Re: Installation Problem

[Lisi Reisz]

On Wednesday 28 October 2015 14:56:51 Ssov Samoht wrote:
> Hello,
>
> Ive recently been trying to install Debian Kali Linux

"Debian Kali Linux" doesn't actually exist.  Debian GNU/Linux exists.  Kali 
Linux exists.  Kali Linux is based on Debian (how loosely??).  Debian != 
Kali.

> and it takes me a 
> long time to install it but when its done it just goes back to the starting
> screen and all i can select it
>
> Install
> Advanced Options
> Help
> Install with speech synthesis
>
> Please help me ):

The suggestion that you may not have ejected the install media sounds a good 
one.

Lisi

Re: jessie installation problem on arm sheevaplug

[Rick Thomas]

On Jun 8, 2015, at 7:01 AM, Martin Michlmayr t...@cyrius.com wrote:

 * Rick Thomas rbtho...@pobox.com [2015-06-07 19:39]:
 I’ve attached a screenlog file from “screen -L /dev/ttyUSB0 115200”
 if that’s any help.  The VT100-style curses stuff makes it a bit
 hard to interpret…
 
 From the log it looks like you didn't finish the installation.  These
 are the last messages in the log:
 
 Abort the installation
 
 If you have not finished the install, your system may be left in an
 unusable state.
 
 Are you sure you want to exit now?
 
 The system is going down NOW!
 
 -- 
 Martin Michlmayr
 http://www.cyrius.com/
 

As I said, I don’t know what went wrong, but the installer encountered a 
persistent error in the ‘make the system bootable’ stage.

When I saw that it wasn’t going any further, I aborted the install, as you 
rightly point out.

The actual problem occurred a bit before the end of the log.  But all the VT100 
ncurses stuff makes it difficult to tell what’s going on from the log.

As I noted in the followup, I tried again.  This time it worked perfectly.

So I guess my problem was some kind of a transient thing and should be ignored. 
 Sorry for the noise!  /-:

Enjoy!
Rick

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/51d43607-222b-4b1d-9f8a-e51843d4f...@pobox.com

Re: jessie installation problem on arm sheevaplug

[Rick Thomas]

On Jun 7, 2015, at 7:39 PM, Rick Thomas rbtho...@pobox.com wrote:

 
 On Jun 6, 2015, at 10:55 AM, Martin Michlmayr t...@cyrius.com wrote:
 
 * Rodrigo Valiña Gutiérrez rodr...@gmail.com [2015-05-18 13:42]:
 The relevant part of /var/log/installer/syslog seems to be this:
 ...
 May 17 15:19:13 base-installer: info: could not determine kernel flavour
 
 The installer is fixed now and you can install Debian on the
 SheevaPlug (and other plug variants) again.
 
 -- 
 Martin Michlmayr
 http://www.cyrius.com/
 
 Hi Martin!
 
 I followed the directions at 
 http://www.cyrius.com/debian/kirkwood/sheevaplug/
 and
 http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/
 
 All went well until, near the end of the installation, it came to “make the 
 system bootable”.
 At that point it got an error and refused to continue.
 
 The setup was a 16GB USB flash-stick with the uImage and uInitrd on it, which 
 was re-used as system residency during the installation partition.
 
 What have I done wrong?
 
 Thanks!
 Rick
 
 I’ve attached a screenlog file from “screen -L /dev/ttyUSB0 115200” if that’s 
 any help.  The VT100-style curses stuff makes it a bit hard to interpret…
 
 FAILEDscreenlog

H…

I tried again.  This time I did *not* upgrade u-boot.  I used ‘U-Boot 2011.12 
(Mar 11 2012 - 18:59:46)’ which I had already installed sometime earlier.  
Everything worked flawlessly this time!

I tweaked the u-boot environment post-install setup in two ways:

1) I changed $(bootargs_console) to ${bootargs_console}.
2) I added ‘mmc init;’ to the beginning of bootcmd_mmc.

I have no idea what went wrong the first time I tried…

A thousand thanks for all your help and dedication!

Rick



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/44296a1f-1ac5-48ef-96fa-0e74b0995...@pobox.com

Re: jessie installation problem on arm sheevaplug

[Martin Michlmayr]

* Rick Thomas rbtho...@pobox.com [2015-06-07 19:39]:
 I’ve attached a screenlog file from “screen -L /dev/ttyUSB0 115200”
 if that’s any help.  The VT100-style curses stuff makes it a bit
 hard to interpret…

From the log it looks like you didn't finish the installation.  These
are the last messages in the log:

Abort the installation

If you have not finished the install, your system may be left in an
unusable state.

Are you sure you want to exit now?

The system is going down NOW!

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150608140120.gb17...@jirafa.cyrius.com

Re: Re: Re: jessie installation problem on arm sheevaplug

[Martin Michlmayr]

* Rodrigo Valiña Gutiérrez rodr...@gmail.com [2015-05-18 13:42]:
 The relevant part of /var/log/installer/syslog seems to be this:
...
 May 17 15:19:13 base-installer: info: could not determine kernel flavour

The installer is fixed now and you can install Debian on the
SheevaPlug (and other plug variants) again.

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150606175503.ga6...@jirafa.cyrius.com

Re: Re: Re: jessie installation problem on arm sheevaplug

[Rodrigo Valiña Gutiérrez]

 But now the installer fails in the Install the base system step,
 saying: No installable kernel was found in the defined APT sources...
 when the last time I tested with changed machid and original uImage it
 worked with the same sources.

What does /var/log/syslog say when this happens?

I managed to complete the installation by continuing without a kernel
and when the
'make the system bootable' step failed, go to a shell and exec
'apt-install linux-image-kirkwood', and then rerun the 'make the
system bootable' step.
It seems to complete well the installation.
Although I changed in /etc/initramfs-tools/initramfs.conf:
MODULES=most - MODULES=dep,
because by default the installer chooses 'targeted' but when I
installed the kernel
it seems it chosed 'generic' initramfs. (both options booted ok).

The relevant part of /var/log/installer/syslog seems to be this:

May 17 15:18:57 in-target: Generating locales (this might take a while)...^M
May 17 15:18:57 in-target: Generation complete.
May 17 15:18:57 in-target: ^M
May 17 15:19:01 localechooser: Adding locale 'en_US.UTF-8'
May 17 15:19:01 localechooser: Generating added locales...
May 17 15:19:13 base-installer: info: could not determine kernel flavour
May 17 15:19:13 base-installer: info: could not determine kernel flavour
May 17 15:19:13 base-installer: info: could not determine kernel flavour
May 17 15:19:13 base-installer: info: could not determine kernel flavour
May 17 15:19:13 base-installer: info: could not determine kernel flavour
May 17 15:19:13 base-installer: info: could not determine kernel flavour
May 17 15:19:13 base-installer: info: could not determine kernel flavour
May 17 15:19:13 base-installer: info: could not determine kernel flavour
May 17 15:19:13 base-installer: info: Found kernels ''
May 17 17:59:53 base-installer: info: Not installing any kernel
May 17 17:59:53 base-installer: info: Installing queued packages into /target/.
May 17 17:59:55 in-target: Reading package lists...
May 17 17:59:55 in-target:

Re: Re: jessie installation problem on arm sheevaplug

[Rodrigo Valiña Gutiérrez]

Does this boot?

This is how I prepare the image:

wget 
http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/device-tree/kirkwood-sheevaplug.dtb
wget 
http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uImage
# Remove the u-boot header
dd if=uImage of=kernel.without bs=1 skip=64
rm -f uImage
# Append device tree
cat kirkwood-sheevaplug.dtb  kernel.without
# Create new uImage
sudo apt-get install u-boot-tools
mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n 
Debian kernel -d kernel.without uImage

Thanks Martin...
I have tested this way of preparation of the image and it booted well
(no need to set machid).

But now the installer fails in the Install the base system step,
saying: No installable kernel was found in the defined APT sources...
when the last time I tested with changed machid and original uImage it
worked with the same sources.

May be needed to set mainlineLinux or arcNumber environment variables?
I do not have them set currently.

Re: Re: jessie installation problem on arm sheevaplug

[Martin Michlmayr]

* Rodrigo Valiña Gutiérrez rodr...@gmail.com [2015-05-17 16:09]:
 But now the installer fails in the Install the base system step,
 saying: No installable kernel was found in the defined APT sources...
 when the last time I tested with changed machid and original uImage it
 worked with the same sources.

What does /var/log/syslog say when this happens?

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150517232447.gb9...@jirafa.cyrius.com

Re: jessie installation problem on arm sheevaplug

[Rodrigo Valiña Gutiérrez]

I had the same problem installing Debian 8 'Jessie' on a SheevaPlug.

I solved it temporarily by doing the following:

- In u-boot:

setenv machid 0692
saveenv

- Then install normally. The 'make the system bootable' phase will fail
because flash-kernel fails:
 /var/log/installer/syslog:
May 16 13:47:28 in-target: Setting up u-boot-tools (2014.10+dfsg1-5) ...^M
4-kirkwood
May 16 13:47:46 in-target: Unsupported platform.
May 16 13:47:46 flash-kernel-installer: error: flash-kernel failed
May 16 13:47:46 main-menu[170]: WARNING **: Configuring
'flash-kernel-installer' failed with error code 1
May 16 13:47:46 main-menu[170]: WARNING **: Menu item
'flash-kernel-installer' failed.


- Then select 'execute a shell' and write:

cd /target/boot/
/target/usr/bin/mkimage -A arm -O linux -T kernel  -C none -n uImage  -a
0x8000 -e 0x8000 -d vmlinuz uImage
/target/usr/bin/mkimage -A arm -O linux -T ramdisk -C none -n
uInitrd -d initrd.img  uInitrd

- It may be neccesary to change 0x8000 to 0x0080 in both cases, but
in my case it worked the way above.
- Then 'exit' the shell and select 'continue without boot loader'.
- I think that this last phase of mkimage should be repeated on every
kernel upgrade because I think flash-kernel (which calls mkimage) will fail
again.

Re: jessie installation problem on arm sheevaplug

[Rick Thomas]

On May 16, 2015, at 10:33 AM, Rodrigo Valiña Gutiérrez rodr...@gmail.com 
wrote:

 I had the same problem installing Debian 8 'Jessie' on a SheevaPlug.
 
 I solved it temporarily by doing the following:
 
 - In u-boot:
 
 setenv machid 0692
 saveenv
 
 - Then install normally. The 'make the system bootable' phase will fail 
 because flash-kernel fails:
  /var/log/installer/syslog:
 May 16 13:47:28 in-target: Setting up u-boot-tools (2014.10+dfsg1-5) ...^M
 4-kirkwood
 May 16 13:47:46 in-target: Unsupported platform.
 May 16 13:47:46 flash-kernel-installer: error: flash-kernel failed
 May 16 13:47:46 main-menu[170]: WARNING **: Configuring 
 'flash-kernel-installer' failed with error code 1
 May 16 13:47:46 main-menu[170]: WARNING **: Menu item 
 'flash-kernel-installer' failed.
 
 
 - Then select 'execute a shell' and write:
 
 cd /target/boot/
 /target/usr/bin/mkimage -A arm -O linux -T kernel  -C none -n uImage  -a 
 0x8000 -e 0x8000 -d vmlinuz uImage
 /target/usr/bin/mkimage -A arm -O linux -T ramdisk -C none -n uInitrd 
 -d initrd.img  uInitrd
 
 - It may be neccesary to change 0x8000 to 0x0080 in both cases, but 
 in my case it worked the way above.
 - Then 'exit' the shell and select 'continue without boot loader'.
 - I think that this last phase of mkimage should be repeated on every kernel 
 upgrade because I think flash-kernel (which calls mkimage) will fail again.

Thanks for the analysis, Rodrigo!

Could you submit a bug report against uboot-mkimage so the rest of us users of 
sheevaplug devices can get a working system without having to work-around this 
bug?  I think it’s just a matter of having mkimage recognize the sheevaplug’s 
machid as valid, but I’m not an expert.

Hopefully!
Rick

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/341975e0-fffd-4480-a9ad-944fd06d2...@pobox.com

Re: jessie installation problem on arm sheevaplug

[Martin Michlmayr]

* Rick Thomas rbtho...@pobox.com [2015-05-16 17:47]:
  - In u-boot:
  
  setenv machid 0692
  saveenv

This is not the correct solution.

The problem is that there are different ways to boot on ARM machines.
The old way was for the boot loader to pass a machine ID to the kernel
which would tell the kernel which machine it's running on.  The new
way requires u-boot to pass a device tree to the kernel which
describes the hardware components of the system. (The workaround
suggested here simply tells the kernel a wrong machine ID and that
works because that particular device has not been converted over to
device tree yet, but this is not a good solution since you're telling
the kernel a wrong device, so it's possible some hardware components
won't work correctly.)

The u-boot in Debian passes the machine ID (because that's how you
configured it) but not the device tree.  Newer kernels require the
device tree on the SheevaPlug and no longer support the machine ID,
which is why you get the error about the machine ID not being known.

Ideally, u-boot would pass the device tree to the kernel, but this is
currently not done in Debian's u-boot (see #782293).

So the best solution now is to append the device tree blob (DTB) to
the kernel in the installer.  This way, the kernel will find the
correct device tree and can boot (and everything else will work since
flash-kernel already appends the DTB on the SheevaPlug).

I've to catch a flight now but I'll post a kernel image with the DTB
tomorrow.

Sorry for not fixing this earlier.

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150517013718.ga5...@jirafa.cyrius.com

Re: jessie installation problem on arm sheevaplug

[Martin Michlmayr]

* Martin Michlmayr t...@cyrius.com [2015-05-16 21:37]:
 So the best solution now is to append the device tree blob (DTB) to
 the kernel in the installer.  This way, the kernel will find the
 correct device tree and can boot (and everything else will work since
 flash-kernel already appends the DTB on the SheevaPlug).

Here's a test image.

Take the kernel from http://www.cyrius.com/tmp/sheevaplug/uImage
Take the ramdisk from 
http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uInitrd
Boot it as described here: 
http://www.cyrius.com/debian/kirkwood/sheevaplug/install/

Does this boot?

This is how I prepare the image:

wget 
http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/device-tree/kirkwood-sheevaplug.dtb
wget 
http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uImage
# Remove the u-boot header
dd if=uImage of=kernel.without bs=1 skip=64
rm -f uImage
# Append device tree
cat kirkwood-sheevaplug.dtb  kernel.without
# Create new uImage
sudo apt-get install u-boot-tools
mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n 
Debian kernel -d kernel.without uImage

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150517015607.ga6...@jirafa.cyrius.com

Re: Re: jessie installation problem on arm sheevaplug

[Rodrigo Valiña Gutiérrez]

I am not an expert...

The workaround just worked, but I don't know whether 0692
Marvell RD-88F6281 Reference Board
is a valid machid for the sheevaplug, instead of the 'original' 0831.

At the beggining it worked, but now I have a problem: the sheevaplug
ethernet subsystem does not work well...
It does not get an IP by DHCP and assigning a static one does not work either...
I suspect that is caused by the workaround but I don't know.

So I do not recommend doing the procedure/workaround of changing machid,
as it may be unsafe and I warn thay may damage the hardware.

I hope Martin's solution will work... Where will you post the kernel image?

jessie installation problem on arm sheevaplug

[henri dugenou]

Hello

I'm trying to install debian 8.0 (jessie) on a Sheevaplug
I follow the guide of Martin Michlmayr
 I don't succeed
down is the capture of the output

note the same procedure for wheezy was successfull

some help would be appreciated
(sorry for my english)

rb

*
U-Boot 2011.12 (Mar 11 2012 - 18:59:46)
Marvell-Sheevaplug - eSATA - SD/MMC

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
In:serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0

Marvell usb start
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
   scanning bus for storage devices... 1 Storage Device(s) found
Marvell fatload usb 0:1 0x0080 /uImage8
reading /uImage8

2071448 bytes read
Marvell fatload usb 0:1 0x0110 /uInitrd8
reading /uInitrd8

5367048 bytes read
Marvell setenv bootargs console=ttyS0,115200n8
base-installer/initramfs-tools/driver-policy=mt
Marvell bootm 0x0080 0x0110
## Booting kernel from Legacy Image at 0080 ...
   Image Name:   Debian kernel
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:2071384 Bytes = 2 MiB
   Load Address: 8000
   Entry Point:  8000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 0110 ...
   Image Name:   debian-installer ramdisk
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:5366984 Bytes = 5.1 MiB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x0831).

Available machine support:

ID (hex)NAME
089bLaCie d2 Network v2
089eLaCie 5Big Network v2
089cLaCie 2Big Network v2
0b44Marvell OpenRD Ultimate Board
0939Marvell OpenRD Client Board
0915Marvell OpenRD Base Board
0691Marvell RD-88F6192-NAS Development Board
0692Marvell RD-88F6281 Reference Board
0b1eHP t5325 Thin Client
085bQNAP TS-119/TS-219
09c6QNAP TS-41x
Marvell Kirkwood (Flattened Device Tree)

Please check your kernel config and/or bootloader.
***

-- 
 

L'adresse électronique (adel/email) qui figure dans ce message constitue une 
donnée personnelle telle que définie par la Loi.
Aussi, nous nous opposons formellement à son utilisation ou à son 
enregistrement non _expressément autorisés_ par nos soins.
(Le fait que cette adresse figure dans un message ne constitue pas une telle 
autorisation)
Afin d'éviter la constitution de liste(s) d'adresses à notre insu, en cas 
d'envoi d'un même message à plusieurs personnes, veuillez diffuser votre 
message en COPIE CACHÉE ( Bcc / Cci / copie conforme invisible).
De même, nous vous demandons de conserver, le cas échéant, cette adresse dans 
un lieu sûr.
...
Ensemble, luttons contre le spam (pourriel) voir www.caspam.org par exemple, et 
aussi www.cnil.fr
_*NON aux brevets logiciels*_ cf www.ffii.fr et http://petition.eurolinux.org
refusons les fichiers aux formats /propriétaires/ (.doc, .xls, ...)
utilisons des fichiers aux formats *ouverts* (.rtf, .pdf, .html ...)
Vivent les logiciels libres ! ;-)
bureautique: LibreOffice.org (gratuit) ... http://fr.libreoffice.org
navigateur: FirefoX (gratuit) ... http://www.mozilla-europe.org
courriel: Thunderbird (gratuit) ... http://www.mozilla-europe.org 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55536c26.30...@mageos.com

AMD RADEON HD 7500/7600 driver installation problem in Debian Wheezy

[Devajit Asem]

Hi..Debian Developers i tried to install amd catalyst graphics driver
for my *HP-Notebook* with specifications as follows:
*lspci | grep VGA*
00:02.0 VGA compatible controller:* Intel Corporation 3rd Gen Core
processor Graphics Controller (rev 09)* 01:00.0 VGA compatible
controller: *Advanced
Micro Devices [AMD] nee ATI Thames XT/GL [Radeon HD 7600M Series*

I already tried installing with instructions from *
https://wiki.debian.org/ATIProprietary* n got error like this:

Loading new fglrx-12-6+point DKMS files... First Installation: checking all
kernels... Building only for 3.7-trunk-686-pae Building initial module for
3.7-trunk-686-pae
*Error! Bad return status for module build on kernel: 3.7-trunk-686-pae
(i686)*
Consult /var/lib/dkms/fglrx/12-6+point/build/make.log for more information.
*dpkg: error processing fglrx-modules-dkms (--configure):
subprocess installed post-installation script returned error exit status 10
Errors were encountered while processing: fglrx-modules-dkms*

After that i installed with proper instructions from forums
*amd-catalyst-13.10-beta2-linux-x86.x86_64.zip*
which is of no luck for me

then i installed
*amd-driver-installer-catalyst-13-4-linux-x86.x86_64.zip*
but this time the installer says I've successfully completed installation
and gave me a prompt to reboot the system n i did it. When i boot up the
system, it jst displays a black screen with sort of underline cursor n i'm
not able to do anything. I didnt change or configure xorg.conf after the
installation...
So please help me.
i really need to install thus.
Thanks in advance.

Re: AMD RADEON HD 7500/7600 driver installation problem in Debian Wheezy

[Ralf Mardorf]

On Mon, 2013-10-21 at 01:01 +0530, Devajit Asem wrote:
 Hi..Debian Developers

Most on this list are users as you and me.

Please post the output of

grep EE /var/log/Xorg.0.log



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1382299004.9040.21.camel@archlinux

Re: AMD RADEON HD 7500/7600 driver installation problem in Debian Wheezy

[Paul Cartwright]

  
  
On 10/20/2013 03:31 PM, Devajit Asem
  wrote:

amd-driver-installer-catalyst-13-4-linux-x86.x86_64.zip
  but this time the installer says I've successfully completed
  installation and gave me a prompt to reboot the system n i did it.
  When i boot up the system, it jst displays a black screen with
  sort of underline cursor n i'm not able to do anything.
  I didnt change or configure xorg.conf after the installation...
I installed that recently, I have the HD 5600 card. I also got the
black screen, so I shut it off, waitied 30 seconds. When I rebooted
again it was fine.

-- 
Paul Cartwright
Registered Linux User #367800 and new counter #561587
  



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5264458e.5080...@gmail.com

Linux 5.0 and 6.0 squeeze installation problem

[wael kaddouh]

Good day guys,

Got the Debian 5 Lenny tried installing it ona  g8 380p proliant server,
but i got the the cd-rom drive contains a cd which cannot be used for
installation thought it was an OS problem , tried istalling squeeze 6.0
same problem, tried burning the OS on a USB stick again same problem. Am
banging my head against the wall here. help please

Re: Linux 5.0 and 6.0 squeeze installation problem

[Lisi Reisz]

On Thursday 26 September 2013 09:23:37 wael kaddouh wrote:
 Good day guys,

 Got the Debian 5 Lenny tried installing it ona  g8 380p proliant
 server, but i got the the cd-rom drive contains a cd which cannot
 be used for installation thought it was an OS problem , tried
 istalling squeeze 6.0 same problem, tried burning the OS on a USB
 stick again same problem. Am banging my head against the wall here.
 help please

Those are both old versions that are not easy (utterly straightforward 
if you prefer) to install now.  Is there a reason why you want an old 
version?  Otherwise use the current Stable, Wheezy, Debian 7, or even 
Jessie, the current testing.

When you say that you got the CDs, what do you mean?  Did you burn 
them yourself?  Did you burn and image or copy the files?  It sounds 
rather as though you may have copied the files, given the error 
message you are getting.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201309261658.49699.lisi.re...@gmail.com

ERRATUM: Re: Linux 5.0 and 6.0 squeeze installation problem

[Lisi Reisz]

On Thursday 26 September 2013 16:58:49 Lisi Reisz wrote:
 Did you burn and image or copy the files?

Sorry.  Burn **an** image

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201309261708.37254.lisi.re...@gmail.com

Re: Debian 6.06 Installation Problem

[Darac Marjal]

On Tue, Jul 09, 2013 at 10:28:43AM +0530, Indrajit Gohain wrote:
Hi,
 
I have a IBM System X 3650 M4 model server. I try to install Operating
System Debian 6.06 . Problem arises when installation complete cd eject
and reboot the system.
After rebooting the system the os not load from hard drive. System
restarting again and again...

How far does the booting get you? Does the BIOS check complete? Do you
get the GRUB menu (something like this:
http://screenshots.debian.net/package/grub or possibly with a background
image)? Does the kernel begin booting? Does it get as far as init?

A quick bit of searching suggests to me that your machine may have an
64-bit processor? For that, you should have installed either the i386 or
amd64 variants.

I try with RAID 0,RAID 1 and RAID 10.

For RAID 1 and above, try to install GRUB on all disks.


signature.asc
Description: Digital signature

Debian 6.06 Installation Problem

[Indrajit Gohain]

Hi,

I have a IBM System X 3650 M4 model server. I try to install Operating
System Debian 6.06 . Problem arises when installation complete cd eject and
reboot the system.
After rebooting the system the os not load from hard drive. System
restarting again and again...
I try with RAID 0,RAID 1 and RAID 10.

Please help.

Thanks  Regards
Indrajit Gohain

[SOLVED] Re: Wheezy installation problem

[Lucio Crusca]

As they told me on debian-boot list, the problem was being 
caused by bug #696942 which has been fixed in yesterday weekly 
iso image of wheezy.

It now works, tanks.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/keqid3$2u2$1...@ger.gmane.org

Re: Wheezy installation problem

[Andrei POPESCU]

On Sb, 02 feb 13, 21:41:15, Lucio Crusca wrote:
 
 The installation starts normally, it leads me through all the steps, it 
 formats the filesystem, copies files, but in the end GRUB installation 
 fails. I've tried both UEFI and CSM bios settings with no luck, always same 
 error:
... 
 Any clues?

I'd say you should contact debian-boot if you don't get any useful hints 
here.

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: Wheezy installation problem

[Lucio Crusca]

Petr Voralek wrote:
   What did you use as partition table type?  

Tried both gpt and msdos (which I assume to actually be mbr), same error.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/kels2t$teb$1...@ger.gmane.org

Re: Wheezy installation problem

[Bob Proulx]

Lucio Crusca wrote:
 The installation starts normally, it leads me through all the steps, it 
 formats the filesystem, copies files, but in the end GRUB installation 
 fails. I've tried both UEFI and CSM bios settings with no luck, always same 
 error:
 
  [!!] install GRUB boot loader on disk
 Installation step failed
 
 or something like that, I just can't copy and paste.
 
 Unfortunately even the 4th console does not say anything useful, like the 
 reason why it failed. Dmesg doesn't say a thing about this.

The only time I have ever had this problem was with a previous Debian
release (Etch 4.0 or Lenny 5.0, don't remember) and setting up the
root filesystem on lvm *without* a separate /boot partition.  However
I believe that is handled correctly with the current release and
later.

But this leads me to believe that the problem must be associated with
how the disk is partitioned.  And since you are setting up raid that
will be the most complicated choices made during operating the
installer.

 I have two SATA disks 1TB each in software RAID, but I've already tried 
 using only one disk without raid and with only 1 partition and obtained the 
 same error.

That would have been my suggestion.  If you didn't select the simplest
options then I would double check with a single disk and make sure
that there isn't any raid or lvm being used for the simple test.

My next suggestion would be to use the install media as a rescue
system.  (I have been suggesting that a lot lately.  Sorry for being
so repetitive but it seems useful here too.)  Here about half way down
this previous posting is where I described it in most detail so I
won't repeat that part here again.

  http://lists.debian.org/debian-user/2013/01/msg01127.html

After booting the rescue and launching a full bash shell you should be
able to have access to the network and to run full commands.  That
will be useful for debugging.  You can run commands and save off the
output as needed.  I would typically set up remote sshd login
capability and log in remotely from another machine and debug from
there.  Can then cut and paste easily.  In either case you should be
able to run 'grub-install' manually from the command line at that
point and any errors it produces will be immediately available.

  root@example:~# grub-install /dev/sda

If it produces any errors those will now be visible directly without
the debian-installer needing to be in the middle of the interface.

Bob


signature.asc
Description: Digital signature

Wheezy installation problem

[Lucio Crusca]

Hi everybody,

I'm trying to install Debian Wheezy amd64 (January 28 iso file) on a new pc 
I've just assembled. The mainboard is an Asus Sabertooth 990FX R2.0, with 
AMD 990fx/SB950 chipset. The CPU is an AMD FX-8350 and I have 16GB of RAM, 
so I'd prefer to avoid the 32bit version of the system if possible.

The installation starts normally, it leads me through all the steps, it 
formats the filesystem, copies files, but in the end GRUB installation 
fails. I've tried both UEFI and CSM bios settings with no luck, always same 
error:

 [!!] install GRUB boot loader on disk
Installation step failed

or something like that, I just can't copy and paste.

Unfortunately even the 4th console does not say anything useful, like the 
reason why it failed. Dmesg doesn't say a thing about this.

I have two SATA disks 1TB each in software RAID, but I've already tried 
using only one disk without raid and with only 1 partition and obtained the 
same error.

Any clues?



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/kejtl9$tl4$1...@ger.gmane.org

Re: Wheezy installation problem

[Petr Voralek]

   Hello!

  On 02/02/2013 09:50 PM, *Lucio Crusca* wrote, and I quote (in part):

 The installation starts normally, it leads me through all the steps, it 
 formats the filesystem, copies files, but in the end GRUB installation 
 fails. I've tried both UEFI and CSM bios settings with no luck, always same 
 error:
 
  [!!] install GRUB boot loader on disk
 Installation step failed

  What did you use as partition table type?  I had similar problems when
using gpt (so I used msdos partition table), but it was an older amd64
laptop...

-- 
Petr Voralek(JabberID: na...@jabber.cz)

... Lord, what fools these mortals be!  (William Shakespeare, A
Midsummer-Night's Dream)



signature.asc
Description: OpenPGP digital signature

Re: Can't fix doc-base installation problem

[Tom Furie]

On Wed, Nov 21, 2012 at 04:19:28PM -0800, Gary Roach wrote:

root@mycomputer:/etc/doc-base# aptitude reinstall doc-base
 
 It seems that some files are missing (install-docs?) but I can't
 determine what they  are or where they are. Some help, plese.

Install-docs belongs to package doc-base. Doc-base can't be
re-installed, because it isn't currently installed. What happens when
you run aptitude install doc-base?

If that doesn't work, you could try Osamu's advice.

Cheers,
Tom

-- 
A real friend isn't someone you use once and then throw away.
A real friend is someone you can use over and over again.


signature.asc
Description: Digital signature

Re: Can't fix doc-base installation problem (DONE)

[Gary Roach]

On 11/22/2012 03:46 AM, Tom Furie wrote:

On Wed, Nov 21, 2012 at 04:19:28PM -0800, Gary Roach wrote:

   

root@mycomputer:/etc/doc-base# aptitude reinstall doc-base

It seems that some files are missing (install-docs?) but I can't
determine what they  are or where they are. Some help, plese.
 

Install-docs belongs to package doc-base. Doc-base can't be
re-installed, because it isn't currently installed. What happens when
you run aptitude install doc-base?

If that doesn't work, you could try Osamu's advice.

Cheers,
Tom

   
Sorry to have bothered all of you and appreciate your effort. I'm trying 
to restore a system from cold iron and am having difficulty with 
Backuppc's restore functions. I started comparing files with another 
(supposedly identical) system and found all sorts of discrepancies. I'm 
re-formatting and re-installing everything again.


Thanks for your efforts.

Gary R.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/50ae749d.2020...@verizon.net

Re: Can;t fix doc-base installation problem

[Gary Roach]

On 11/20/2012 10:49 AM, Gary Roach wrote:

Hi everyone:

I've had to restore one of my systems from cold iron. Aptitude seems 
to be hanging up when trying to install / purge / update doc-base. 
I've tried Aptitude, dpkg and apt-get including the -f switch with no  
joy. Below is a typical example:


root@mycomputer:/home/gary# aptitude purge doc-base
The following packages will be REMOVED:
  doc-base{p}
0 packages upgraded, 0 newly installed, 1 to remove and 0 not
upgraded.
Need to get 0 B of archives. After unpacking 504 kB will be freed.
Do you want to continue? [Y/n/?]
(Reading database ... 297009 files and directories currently
installed.)
Removing doc-base ...
cannot find install-docs on path
dpkg: error processing doc-base (--purge):
 subprocess installed pre-removal script returned error exit status 1
configured to not write apport reports
  Errors were encountered
while processing:
 doc-base
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:

root@mycomputer:/home/gary#

I have tried cleaning and reloading the archives. That didn't help. 
The whole dpkg process seems to be hung up at this point. If I try to 
process any other packages, the installation process always returns to 
some variation of the above. The package seems to be partially 
installed. The C flag is set in aptitude. A not configured error is 
sometime displayed. Any suggestions?


Thanks in advance

Gary R.



Since there has been no reply to my query, I am including more 
information in hopes that someone will have an idea how to fix this 
problem. I am completely stumped. This is a Debian Squeeze system using 
KDE. When trying to fix the problem, I got the following:


   root@mycomputer:/var/log# dpkg -C
   The following packages are only half configured, probably due to
   problems
   configuring them the first time.  The configuration should be
   retried using
   dpkg --configure package or the configure menu option in dselect:
 doc-base utilities to manage online documentation

   root@mycomputer:/var/log# dpkg --configure doc-base
   Setting up doc-base (0.9.5) ...
   /var/lib/dpkg/info/doc-base.postinst: 45: install-docs: not found
   dpkg: error processing doc-base (--configure):
 subprocess installed post-installation script returned error exit
   status 127
   Errors were encountered while processing:
 doc-base

   root@mycomputer:/var/log# dpkg-query -s doc-base
   Package: doc-base
   Status: purge ok half-configured
   Priority: optional
   Section: doc
   Installed-Size: 492
   Maintainer: Robert Luberda rob...@debian.org
   Architecture: all
   Version: 0.9.5
   Config-Version: 0.9.5
   Depends: perl, libuuid-perl, dpkg (= 1.14.17), libmldbm-perl
   Suggests: dhelp | dwww | doc-central | yelp | khelpcenter4,
   rarian-compat
   Conflicts: dhelp ( 0.6.7), dwww ( 1.10.13~)
   Conffiles:
 /etc/doc-base/documents/README efd9c153645bd3e0653eb5b0fbeda91f
   Description: utilities to manage online documentation
 This package contains utilities to manage documentation installed on
 a Debian system. It generates a database of document metadata, which
 other packages such as dwww, dhelp, doc-central, and rarian-compat
 can use to provide a catalog of available documentation.
 .
 For additional information see the Debian doc-base Manual included in
 this package.


   root@mycomputer:/etc/doc-base# aptitude purge doc-base
   The following packages will be REMOVED:
  doc-base{p}
   0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
   Need to get 0 B of archives. After unpacking 504 kB will be freed.
   Do you want to continue? [Y/n/?]
   (Reading database ... 297009 files and directories currently installed.)
   Removing doc-base ...
   cannot find install-docs on path
   dpkg: error processing doc-base (--purge):
 subprocess installed pre-removal script returned error exit status 1
   configured to not write apport reports
  Errors were encountered while
   processing:
 doc-base
   E: Sub-process /usr/bin/dpkg returned an error code (1)
   A package failed to install.  Trying to recover:

   root@mycomputer:/etc/doc-base# aptitude reinstall doc-base
   The following packages will be REINSTALLED:
  doc-base
   0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove
   and 0 not upgraded.
   Need to get 0 B of archives. After unpacking 0 B will be used.
   Setting up doc-base (0.9.5) ...
   /var/lib/dpkg/info/doc-base.postinst: 45: install-docs: not found
   dpkg: error processing doc-base (--configure):
 subprocess installed post-installation script returned error exit
   status 127
   configured to not write apport reports
  Errors were encountered while
   processing:
  

Re: Can;t fix doc-base installation problem

[Osamu Aoki]

On Tue, Nov 20, 2012 at 10:49:03AM -0800, Gary Roach wrote:
 Hi everyone:
 
 I've had to restore one of my systems from cold iron. Aptitude seems

I guerss you are using unstable.

 to be hanging up when trying to install / purge / update doc-base.
 I've tried Aptitude, dpkg and apt-get including the -f switch with
 no  joy. Below is a typical example:
 
root@mycomputer:/home/gary# aptitude purge doc-base
The following packages will be REMOVED:
   doc-base{p}

Did you check our BTS?
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648936
This looks like one you hit.

0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 504 kB will be freed.
Do you want to continue? [Y/n/?]
(Reading database ... 297009 files and directories currently installed.)
Removing doc-base ...


Now calling 
 /var/lib/dpkg/info/doc-base.prerm

cannot find install-docs on path

This is the problem.

If I were you, I will try following as work around.  But before doing
this, check all discussion on the above mentioned BTS.  There may be
better ways.

You should see in /var/lib/dpkg/info/doc-base.prerm:
case $1 in
remove)
remove_all_docs
;;
upgrade)
;;
failed-upgrade)
# Prepare to upgrade from version $2 of this package TO THIS VERSION.
# This is only used if the old version's prerm couldn't handle it,
# and returned non-zero.  (Fix old prerm bugs here.)
;;
esac

Edit this to be:

case $1 in
remove)
true
;;
upgrade)
;;
failed-upgrade)
# Prepare to upgrade from version $2 of this package TO THIS VERSION.
# This is only used if the old version's prerm couldn't handle it,
# and returned non-zero.  (Fix old prerm bugs here.)
;;
esac

and try removing this again.  This is just work around.  If there are
other issues, please work around issues.

I think by installing newer version of doc-base, this should fix this.
...


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121121143746.GA23161@goofy.localdomain

Can;t fix doc-base installation problem

[Gary Roach]

Hi everyone:

I've had to restore one of my systems from cold iron. Aptitude seems to 
be hanging up when trying to install / purge / update doc-base. I've 
tried Aptitude, dpkg and apt-get including the -f switch with no  joy. 
Below is a typical example:


   root@mycomputer:/home/gary# aptitude purge doc-base
   The following packages will be REMOVED:
  doc-base{p}
   0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
   Need to get 0 B of archives. After unpacking 504 kB will be freed.
   Do you want to continue? [Y/n/?]
   (Reading database ... 297009 files and directories currently installed.)
   Removing doc-base ...
   cannot find install-docs on path
   dpkg: error processing doc-base (--purge):
 subprocess installed pre-removal script returned error exit status 1
   configured to not write apport reports
  Errors were encountered while
   processing:
 doc-base
   E: Sub-process /usr/bin/dpkg returned an error code (1)
   A package failed to install.  Trying to recover:

   root@mycomputer:/home/gary#

I have tried cleaning and reloading the archives. That didn't help. The 
whole dpkg process seems to be hung up at this point. If I try to 
process any other packages, the installation process always returns to 
some variation of the above. The package seems to be partially 
installed. The C flag is set in aptitude. A not configured error is 
sometime displayed. Any suggestions?


Thanks in advance

Gary R.

Re: Installation problem on Dell Latitude D810

[Tony Baldwin]

On Sun, Oct 07, 2012 at 08:38:14PM +0200, Cesar Enrique Garcia Dabo wrote:
 
  Thanks a lot!
  I have now successfully installed  Debian with image firmware-6.0.6-amd64-
 i386-netinst.iso and it works fine. I used that because I read that my wifi 
 card 
 needs non free firmware. However the WLAN configuration didn't work. The card 
 was detected but when trying to look for access points it wouldn't find any. 
  I ended up using the ethernet cable, but is it normal that it cannot find 
 any 
 wlan network? The firmware seems to be installed, at least it asked to agree 
 on 
 the license...
  Regards,
  Enrique

I've installed Debian on a Dell d420 and a d620, and the wifi and
everything worked awesome right out of the box, without adding non-free
firmware, even.

weird...
Or maybe just the older hardware doesn't require newer/non-free
firmware?

./tony
-- 
http://www.tonybaldwin.me
all tony, all the time!
3F330C6E


signature.asc
Description: Digital signature

Re: Installation problem on Dell Latitude D810

[Cesar Enrique Garcia Dabo]

 Thanks a lot!
 I have now successfully installed  Debian with image firmware-6.0.6-amd64-
i386-netinst.iso and it works fine. I used that because I read that my wifi 
card 
needs non free firmware. However the WLAN configuration didn't work. The card 
was detected but when trying to look for access points it wouldn't find any. 
 I ended up using the ethernet cable, but is it normal that it cannot find any 
wlan network? The firmware seems to be installed, at least it asked to agree on 
the license...
 Regards,
 Enrique

On Saturday 06 October 2012 14:35:50 Brian wrote:
 On Sat 06 Oct 2012 at 15:02:17 +0200, Cesar Enrique Garcia Dabo wrote:
   I am trying to install Debian 6.0 on a rather old laptop Latitude D810.
 
 You are not trying hard enough. :)
 
  However it hangs when detecting network hardware using the graphical
  installer.
 
 Please see below.
 
   On the same machine I was able to boot Fedora 17 without problems.
   I have tried also connecting an ethernet cable but it also hangs.
   
The kernel messages on the same machine using kernel 3.5.3 from F17 are:
  [   16.608061] tg3.c:v3.123 (March 21, 2012)
  [   16.617814] tg3 :02:00.0: eth0: Tigon3 [partno(BCM95751) rev 4001]
  (PCI Express) MAC address 00:14:22:e2:2d:9a
  [   16.617825] tg3 :02:00.0: eth0: attached PHY is 5750
  (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
  [   16.617834] tg3 :02:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0]
  ASF[0] TSOcap[1]
  [   16.617842] tg3 :02:00.0: eth0: dma_rwctrl[7618]
  dma_mask[64-bit] ...
  [   17.285950] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
  1.2.2kmprq
  [   17.285957] ipw2200: Copyright(c) 2003-2006 Intel Corporation
  [   17.286183] ipw2200: Detected Intel PRO/Wireless 2915ABG Network
  Connection 
   I am using image debian-wheezy-DI-b1-i386-netinst.iso.
 
 This is a beta image for Wheezy. What has happened to you is a known bug
 in d-i.
 
   Do you know any way to install it on this laptop?
 
 Use a Squeeze 6.0.5 install image.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5378485.f6YmBOpTJG@psd-laptop1

Re: Installation problem on Dell Latitude D810

[Brian]

On Sun 07 Oct 2012 at 20:38:14 +0200, Cesar Enrique Garcia Dabo wrote:

  I have now successfully installed  Debian with image firmware-6.0.6-amd64-
 i386-netinst.iso and it works fine.

Good.

 I used that because I read that my wifi 
 card 
 needs non free firmware. However the WLAN configuration didn't work. The card 
 was detected but when trying to look for access points it wouldn't find any. 
  I ended up using the ethernet cable, but is it normal that it cannot find 
 any 
 wlan network? The firmware seems to be installed, at least it asked to agree 
 on 
 the license...

Only WEP is available when installing Squeeze. Maybe that was the problem.
Wheezy has WPA and makes a good job of setting up a wireless connection.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121007205455.GE30872@desktop

Installation problem on Dell Latitude D810

[Cesar Enrique Garcia Dabo]

 Hi,

 I am trying to install Debian 6.0 on a rather old laptop Latitude D810. 
However it hangs when detecting network hardware using the graphical 
installer.
 On the same machine I was able to boot Fedora 17 without problems.
 I have tried also connecting an ethernet cable but it also hangs.
  The kernel messages on the same machine using kernel 3.5.3 from F17 are:

[   16.608061] tg3.c:v3.123 (March 21, 2012)
[   16.617814] tg3 :02:00.0: eth0: Tigon3 [partno(BCM95751) rev 4001] (PCI 
Express) MAC address 00:14:22:e2:2d:9a
[   16.617825] tg3 :02:00.0: eth0: attached PHY is 5750 (10/100/1000Base-T 
Ethernet) (WireSpeed[1], EEE[0])
[   16.617834] tg3 :02:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[0] TSOcap[1]
[   16.617842] tg3 :02:00.0: eth0: dma_rwctrl[7618] dma_mask[64-bit]
...
[   17.285950] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 
1.2.2kmprq
[   17.285957] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[   17.286183] ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection

 I am using image debian-wheezy-DI-b1-i386-netinst.iso.
 
 Do you know any way to install it on this laptop?

 Regards,
 Enrique


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/6584801.A9ls6vU17T@psd-laptop1

Re: Installation problem on Dell Latitude D810

[Rob Owens]

On Sat, Oct 06, 2012 at 03:02:17PM +0200, Cesar Enrique Garcia Dabo wrote:
 
 
  Hi,
 
  I am trying to install Debian 6.0 on a rather old laptop Latitude D810. 
 However it hangs when detecting network hardware using the graphical 
 installer.
  On the same machine I was able to boot Fedora 17 without problems.
  I have tried also connecting an ethernet cable but it also hangs.
   The kernel messages on the same machine using kernel 3.5.3 from F17 are:
 
 [   16.608061] tg3.c:v3.123 (March 21, 2012)
 [   16.617814] tg3 :02:00.0: eth0: Tigon3 [partno(BCM95751) rev 4001] 
 (PCI 
 Express) MAC address 00:14:22:e2:2d:9a
 [   16.617825] tg3 :02:00.0: eth0: attached PHY is 5750 
 (10/100/1000Base-T 
 Ethernet) (WireSpeed[1], EEE[0])
 [   16.617834] tg3 :02:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
 ASF[0] TSOcap[1]
 [   16.617842] tg3 :02:00.0: eth0: dma_rwctrl[7618] dma_mask[64-bit]
 ...
 [   17.285950] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 
 1.2.2kmprq
 [   17.285957] ipw2200: Copyright(c) 2003-2006 Intel Corporation
 [   17.286183] ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
 
  I am using image debian-wheezy-DI-b1-i386-netinst.iso.
  
Squeeze is Debian 6.0.  Are you using 6.0 or are you using Wheezy?

I've installed Squeeze on a Dell Latitude 810, using the text installer.
I always had to add 'vga=771' to the boot line, otherwise I got no
display.

-Rob


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121006133414.gb15...@aurora.owens.net