How to install a scanner Canon CanoScan LiDE 220
According to https:/
I am using Ubuntu 16:04 is installed on a lap top Tohiba Dynabook TX 68 H running with a processor Intel® Core™2 Duo CPU P8600 @ 2.40GHz × 2
How to install this scanner?
Thank you for your help.
d
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Manfred Hampl
- Solved:
- Last query:
- Last reply:
|
Revision history for this message
|
#1 |
According to https:/
Connect the scanner to the computer and switch it on, and then issue the commands
dpkg -l | grep sane
sane-find-scanner
sudo sane-find-scanner
What output do you receive?
|
Revision history for this message
|
#2 |
By the way, are you aware that support for Ubuntu 16.04 has already ended a year ago?
Currently that release is in ESM status, which is an extended security support for select server packages only.
You should consider upgrading to a supported Ubuntu release in due course.
|
Revision history for this message
|
#3 |
Thank you very much.
The scanner is powered through the USB slot only.
Here below the output I got from the commands you suggested.
abunaijiji@
ii libsane:i386 1.0.25+git20150528-
1ubuntu2.16.04.3 i386 API library for scanners
ii libsane-common 1.0.25+git20150528-
1ubuntu2.16.04.3 all API library for scanners --
documentation and support files
ii libsane-hpaio:i386 3.16.3+repack0-
1 i386 HP SANE backend for
multi-function peripherals
ii sane-utils 1.0.25+git20150528-
1ubuntu2.16.04.3 i386 API library for scanners --
utilities
abunaijiji@
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make
sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x04a9 [Canon], product=0x190f [CanoScan],
chip=GL848+) at libusb:002:013
could not open USB device 0x1d6b/0x0002 at 002:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 008:001: Access denied
(insufficient permissions)
could not open USB device 0x17ef/0x6018 at 007:002: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 007:001: Access denied
(insufficient permissions)
could not open USB device 0x046d/0xc019 at 006:004: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 006:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 005:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 004:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 003:001: Access denied
(insufficient permissions)
# Your USB scanner was (probably) detected. It may or may not be
supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary
ports
# can't be detected by this program.
# You may want to run this program as root to find all devices. Once
you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
d
2022-04-11 (Mon) の 08:25 +0000 に Manfred Hampl さんは書きました:
> Your question #701288 on Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> According to https:/
> genesys.5.html the sane-genesys driver should work, and that is
> contained in the sane packages in the standard Ubuntu reporitories
>
> Connect the scanner to the computer and switch it on, and then issue
> the
> commands
>
> dpkg -l | grep sane
> sane-find-scanner
> sudo sane-find-scanner
>
> What output do you receive?
>
|
Revision history for this message
|
#4 |
2022-04-11 (Mon) の 08:31 +0000 に Manfred Hampl さんは書きました:
> Your question #701288 on Ubuntu changed:
> https:/
>
> Manfred Hampl posted a new comment:
> By the way, are you aware that support for Ubuntu 16.04 has already
> ended a year ago?
> Currently that release is in ESM status, which is an extended
> security support doe select server packages only.
> You should consider upgrading to a supported Ubuntu release in due
> course.
>
|
Revision history for this message
|
#5 |
Thank you. How to upgrade?
Which version?
Thank you for helps.
2022-04-11 (Mon) の 08:31 +0000 に Manfred Hampl さんは書きました:
> Your question #701288 on Ubuntu changed:
> https:/
>
> Manfred Hampl posted a new comment:
> By the way, are you aware that support for Ubuntu 16.04 has already
> ended a year ago?
> Currently that release is in ESM status, which is an extended
> security support doe select server packages only.
> You should consider upgrading to a supported Ubuntu release in due
> course.
>
|
Revision history for this message
|
#6 |
1.
sane-find-scanner
found USB scanner (vendor=0x04a9 [Canon], product=0x190f [CanoScan],
chip=GL848+) at libusb:002:013
The scanner is identified. Try scanning with the command "xsane"
2.
You seem to be running the 32bit version of Ubuntu fur which support is ending. If your hardware supports it, then you should switch to the 64bit version of Ubuntu.
For diagnostic purposes, what is the output of the command
lscpu
|
Revision history for this message
|
#7 |
Thank you.
1/ Scanner:
Here below:
abunaijiji@
$ dpkg -l | grep xsane
abunaijiji@
No reaction from the PC:
I tried also the following:
abunaijiji@
コマンド 'xsane-
コマンド 'sane-find-scanner' - パッケージ 'sane-utils' (main)
which means:
"do not find the corresponding command".
Command "sane-find-scanner" - package 'sane-utils'(main)
This does not work too.
2/ doing lscpu i got :
> Architecture: i686
> CPU 操作モード: 32-bit, 64-bit
> Byte
> Order: Little Endian
> CPU(s): 2
> On-line CPU(s)
> list: 0,1
> コアあたりのスレッド数:1
> ソケットあたりのコア数:2
> Socket(s): 1
> ベンダー
> ID: GenuineIntel
> CPU ファミリー: 6
> モデル: 23
> Model
> name: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz
> ステッピング:
> 6
> CPU MHz: 1397.268
> CPU max MHz: 2401.0000
> CPU
> min MHz: 800.0000
> BogoMIPS: 4787.47
> 仮想化:
> VT-x
> L1d キャッシュ: 32K
> L1i キャッシュ: 32K
> L2 キャッシュ: 3072K
> Flags:
> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
> constant_tsc arch_perfmon pebs bts cpuid aperfmperf pni dtes64 monitor
> ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm pti
> tpr_shadow vnmi flexpriority dtherm
CPU 操作モード => This should means the CPU swould be able to work in 64
bits mode.
How should I do to upgrade?
d
2022-04-12 (Tue) の 07:15 +0000 に Manfred Hampl さんは書きました:
> Your question #701288 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> 1.
> sane-find-scanner
> found USB scanner (vendor=0x04a9 [Canon], product=0x190f [CanoScan],
> chip=GL848+) at libusb:002:013
>
> The scanner is identified. Try scanning with the command "xsane"
>
> 2.
> You seem to be running the 32bit version of Ubuntu fur which support
> is ending. If your hardware supports it, then you should switch to
> the 64bit version of Ubuntu.
>
> For diagnostic purposes, what is the output of the command
> lscpu
>
|
Revision history for this message
|
#8 |
I asked for the output of the command "sane-find-
And I asked you to run "xsane", but you executed "dpkg -l | grep xsane".
That is not the same.
|
Revision history for this message
|
#9 |
Yes, "CPU 操作モード: 32-bit, 64-bit" tells that your CPU is capable of running 64bit operating systems.
Unfortunately there is no way to upgrade a 32bit system to a 64bit system. This requires a complete new installation.
|
Revision history for this message
|
#10 |
Thank you.
Yes apparently i have to first upgrade to the 18:04 versions and then
to the 20:04 which is 64 bits workable.
https:/
Upgrade paths
Ubuntu supports the ability to upgrade from one LTS to the next LTS
in sequential order. For example, a user on Ubuntu 16.04 LTS can
upgrade
to Ubuntu 18.04 LTS, but cannot jump directly to Ubuntu 20.04 LTS. To
do this, the user would need to upgrade twice: once to Ubuntu 18.04
LTS,
and then upgrade again to Ubuntu 20.04 LTS.
d
2022-04-14 (Thu) の 20:01 +0000 に Manfred Hampl さんは書きました:
> Your question #701288 on Ubuntu changed:
> https:/
>
> Manfred Hampl posted a new comment:
> Yes, "CPU 操作モード: 32-bit, 64-bit" tells that your CPU is capable of
> running 64bit operating systems.
> Unfortunately there is no way to upgrade a 32bit system to a 64bit
> system. This requires a complete new installation.
>
|
Revision history for this message
|
#11 |
Thank you,
abunaijiji@
sane-find: コマンドが見つかりません
which means : don't find the command.
So i ran Xsane and the output indicated i have to run the command sudo
apt install xsane.
abunaijiji@
プログラム 'xsane'
はまだインストールされていません。 次のように入力することでインス
I did and got the following answers:
abunaijiji@
[sudo] abunaijiji のパスワード:
パッケージリストを読み込んでい
依存関係ツリーを作成しています
状態情報を読み取っています... 完了
以下のパッケージが自動でインス
libllvm4.0 snapd-login-service
これを削除するには 'sudo apt autoremove' を利用してください。
以下の追加パッケージがインスト
gimp gimp-data libamd2.4.1 libbabl-0.1-0 libblas-common libblas3
libcamd2.4.1 libccolamd2.9.1 libcholmod3.0.6 libgegl-0.3-0
libgfortran3
libgimp2.0 liblapack3 libsdl1.2debian libumfpack5.7.1 python-cairo
python-gobject-2 python-gtk2 xsane-common
提案パッケージ:
gimp-help-en | gimp-help gimp-data-extras python-
python-gtk2-doc gocr | cuneiform | tesseract-ocr | ocrad gv hylafax-
client
| mgetty-fax
以下のパッケージが新たにインス
gimp gimp-data libamd2.4.1 libbabl-0.1-0 libblas-common libblas3
libcamd2.4.1 libccolamd2.9.1 libcholmod3.0.6 libgegl-0.3-0
libgfortran3
libgimp2.0 liblapack3 libsdl1.2debian libumfpack5.7.1 python-cairo
python-gobject-2 python-gtk2 xsane xsane-common
アップグレード: 0 個、新規インストール: 20 個、削除: 0 個、保留: 0 個。
18.7 MB のアーカイブを取得する必要があります。
この操作後に追加で 98.6 MB のディスク容量が消費されます。
続行しますか? [Y/n] Y
取得:1 http://
libgimp2.0 i386 2.8.16-1ubuntu1.1 [794 kB]
取得:2 http://
gimp-data all 2.8.16-1ubuntu1.1 [7,712 kB]
取得:3 http://
i386 1.8.8-2 [42.7 kB]
取得:4 http://
gobject-2 i386 2.28.6-12ubuntu1 [183 kB]
取得:5 http://
i386 2.24.0-4ubuntu1 [598 kB]
取得:6 http://
0.1-0 i386 0.1.16-1 [251 kB]
取得:7 http://
libsdl1.2debian i386 1.2.15+
kB]
取得:8 http://
i386 1:4.4.6-1 [16.0
kB]
取得:9 http://
common i386 3.6.0-2ubuntu2 [5,338
B]
取得:10 http://
i386 3.6.0-2ubuntu2 [130
kB]
取得:11 http://
i386 1:4.4.6-1 [13.7
kB]
取得:12 http://
libccolamd2.9.1 i386 1:4.4.6-1 [15.0
kB]
取得:13 http://
libgfortran3 i386 5.4.0-6ubuntu1~
kB]
取得:14 http://
i386 3.6.0-2ubuntu2 [1,764
kB]
取得:15 http://
libcholmod3.0.6 i386 1:4.4.6-1 [208
kB]
取得:16 http://
libumfpack5.7.1 i386 1:4.4.6-1 [132
kB]
取得:17 http://
0.3-0 i386 0.3.4-1ubuntu2 [1,062
kB]
取得:18 http://
gimp i386 2.8.16-1ubuntu1.1 [3,624
kB]
取得:19 http://
common all 0.999-3ubuntu1 [1,385
kB]
取得:20 http://
i386 0.999-3ubuntu1 [296
kB]
18.7 MB を 8秒 で取得しました (2,126
kB/s)
以前に未選択のパッケージ libgimp2.0 を選択しています。
(データベースを読み込んでいます ... 現在 221575 個のファイルとディレクトリがイ
.../libgimp2.
libgimp2.0 (2.8.16-1ubuntu1.1) を展開しています...
以前に未選択のパッケージ gimp-data を選択しています。
.../gimp-
gimp-data (2.8.16-1ubuntu1.1) を展開しています...
以前に未選択のパッケージ python-cairo を選択しています。
.../python-
python-cairo (1.8.8-2) を展開しています...
以前に未選択のパッケージ python-gobject-2 を選択しています。
.../python-
python-gobject-2 (2.28.6-12ubuntu1) を展開しています...
以前に未選択のパッケージ python-gtk2 を選択しています。
.../python-
python-gtk2 (2.24.0-4ubuntu1) を展開しています...
以前に未選択のパッケージ libbabl-0.1-0:i386 を選択しています。
.../libbabl-
libbabl-0.1-0:i386 (0.1.16-1) を展開しています...
以前に未選択のパッケージ libsdl1.
.../libsdl1.
libsdl1.
以前に未選択のパッケージ libamd2.4.1:i386 を選択しています。
.../libamd2.
libamd2.4.1:i386 (1:4.4.6-1) を展開しています...
以前に未選択のパッケージ libblas-common を選択しています。
.../libblas-
libblas-common (3.6.0-2ubuntu2) を展開しています...
以前に未選択のパッケージ libblas3 を選択しています。
.../libblas3_
libblas3 (3.6.0-2ubuntu2) を展開しています...
以前に未選択のパッケージ libcamd2.4.1:i386 を選択しています。
.../libcamd2.
libcamd2.4.1:i386 (1:4.4.6-1) を展開しています...
以前に未選択のパッケージ libccolamd2.
.../libccolamd2
libccolamd2.
以前に未選択のパッケージ libgfortran3:i386 を選択しています。
.../libgfortran
libgfortran3:i386 (5.4.0-
以前に未選択のパッケージ liblapack3 を選択しています。
.../liblapack3_
liblapack3 (3.6.0-2ubuntu2) を展開しています...
以前に未選択のパッケージ libcholmod3.
.../libcholmod3
libcholmod3.
以前に未選択のパッケージ libumfpack5.
.../libumfpack5
libumfpack5.
以前に未選択のパッケージ libgegl-0.3-0:i386 を選択しています。
.../libgegl-
libgegl-0.3-0:i386 (0.3.4-1ubuntu2) を展開しています...
以前に未選択のパッケージ gimp を選択しています。
.../gimp_
gimp (2.8.16-1ubuntu1.1) を展開しています...
以前に未選択のパッケージ xsane-common を選択しています。
.../xsane-
xsane-common (0.999-3ubuntu1) を展開しています...
以前に未選択のパッケージ xsane を選択しています。
.../xsane_
xsane (0.999-3ubuntu1) を展開しています...
libc-bin (2.23-0ubuntu11.3) のトリガを処理しています ...
hicolor-icon-theme (0.15-0ubuntu1.1) のトリガを処理しています ...
man-db (2.7.5-1) のトリガを処理しています ...
bamfdaemon (0.5.3~
Rebuilding /usr/share/
desktop-file-utils (0.22-1ubuntu5.2) のトリガを処理しています ...
gnome-menus (3.13.3-6ubuntu3.1) のトリガを処理しています ...
mime-support (3.59ubuntu1) のトリガを処理しています ...
doc-base (0.10.7) のトリガを処理しています ...
doc-base ファイルを 1 個追加 を処理中...
libgimp2.0 (2.8.16-1ubuntu1.1) を設定しています ...
gimp-data (2.8.16-1ubuntu1.1) を設定しています ...
python-cairo (1.8.8-2) を設定しています ...
python-gobject-2 (2.28.6-12ubuntu1) を設定しています ...
python-gtk2 (2.24.0-4ubuntu1) を設定しています ...
libbabl-0.1-0:i386 (0.1.16-1) を設定しています ...
libsdl1.
libamd2.4.1:i386 (1:4.4.6-1) を設定しています ...
libblas-common (3.6.0-2ubuntu2) を設定しています ...
libblas3 (3.6.0-2ubuntu2) を設定しています ...
update-
を提供するために自動モードで /usr/lib/
libcamd2.4.1:i386 (1:4.4.6-1) を設定しています ...
libccolamd2.
libgfortran3:i386 (5.4.0-
liblapack3 (3.6.0-2ubuntu2) を設定しています ...
update-
を提供するために自動モードで /usr/lib/
libcholmod3.
libumfpack5.
libgegl-0.3-0:i386 (0.3.4-1ubuntu2) を設定しています ...
gimp (2.8.16-1ubuntu1.1) を設定しています ...
xsane-common (0.999-3ubuntu1) を設定しています ...
xsane (0.999-3ubuntu1) を設定しています ...
libc-bin (2.23-0ubuntu11.3) のトリガを処理しています ...
abunaijiji@
From this above long output the question what should i do?
Thank you for your help.
2022-04-14 (Thu) の 19:45 +0000 に Manfred Hampl さんは書きました:
> Your question #701288 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> I asked for the output of the command "sane-find-
> executed the command "xsane-
> exist.
>
> And I asked you to run "xsane", but you executed "dpkg -l | grep
> xsane".
> That is not the same.
>
|
Revision history for this message
|
#12 |
Hi again,
I tried the following:
abunaijiji@
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make
sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x04a9 [Canon], product=0x190f [CanoScan],
chip=GL848+) at libusb:002:023
could not open USB device 0x1d6b/0x0002 at 002:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 008:001: Access denied
(insufficient permissions)
could not open USB device 0x17ef/0x6018 at 007:004: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 007:001: Access denied
(insufficient permissions)
could not open USB device 0x046d/0xc019 at 006:004: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 006:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 005:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 004:001: Access denied
(insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 003:001: Access denied
(insufficient permissions)
# Your USB scanner was (probably) detected. It may or may not be
supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary
ports
# can't be detected by this program.
# You may want to run this program as root to find all devices. Once
you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
abunaijiji@
device `genesys:
abunaijiji@
コマンド 'Xsane' は見つかりませんでした。もしかして:
コマンド 'xsane' - パッケージ 'xsane' (universe)
Xsane: コマンドが見つかりません
abunaijiji@
Running "Xsane" I could run the scanner and get an image of the
document scanned. However still a problem to save the image gotten.
Thank you for your help.
d
2022-04-15 (Fri) の 15:36 +0900 に Bourbon さんは書きました:
> Thank you,
>
> abunaijiji@
> sane-find: コマンドが見つかりません
> which means : don't find the command.
> So i ran Xsane and the output indicated i have to run the command
> sudo apt install xsane.
> abunaijiji@
> プログラム 'xsane' はまだインストールされていません。 次のように入力することでインス
> install xsane
>
> I did and got the following answers:
>
> abunaijiji@
> [sudo] abunaijiji のパスワード:
> パッケージリストを読み込んでい
> 依存関係ツリーを作成しています
> 状態情報を読み取っています... 完了
> 以下のパッケージが自動でインス
> libllvm4.0 snapd-login-service
> これを削除するには 'sudo apt autoremove' を利用してください。
> 以下の追加パッケージがインスト
> gimp gimp-data libamd2.4.1 libbabl-0.1-0 libblas-common libblas3
> libcamd2.4.1 libccolamd2.9.1 libcholmod3.0.6 libgegl-0.3-0
> libgfortran3
> libgimp2.0 liblapack3 libsdl1.2debian libumfpack5.7.1 python-cairo
> python-gobject-2 python-gtk2 xsane-common
> 提案パッケージ:
> gimp-help-en | gimp-help gimp-data-extras python-
> python-gtk2-doc gocr | cuneiform | tesseract-ocr | ocrad gv
> hylafax-client
> | mgetty-fax
> 以下のパッケージが新たにインス
> gimp gimp-data libamd2.4.1 libbabl-0.1-0 libblas-common libblas3
> libcamd2.4.1 libccolamd2.9.1 libcholmod3.0.6 libgegl-0.3-0
> libgfortran3
> libgimp2.0 liblapack3 libsdl1.2debian libumfpack5.7.1 python-cairo
> python-gobject-2 python-gtk2 xsane xsane-common
> アップグレード: 0 個、新規インストール: 20 個、削除: 0 個、保留: 0 個。
> 18.7 MB のアーカイブを取得する必要があります。
> この操作後に追加で 98.6 MB のディスク容量が消費されます。
> 続行しますか? [Y/n] Y
> 取得:1 http://
> libgimp2.0 i386 2.8.16-1ubuntu1.1 [794 kB]
> 取得:2 http://
> gimp-data all 2.8.16-1ubuntu1.1 [7,712 kB]
> 取得:3 http://
> cairo i386 1.8.8-2 [42.7 kB]
> 取得:4 http://
> gobject-2 i386 2.28.6-12ubuntu1 [183 kB]
> 取得:5 http://
> i386 2.24.0-4ubuntu1 [598 kB]
> 取得:6 http://
> libbabl-0.1-0 i386 0.1.16-1 [251 kB]
> 取得:7 http://
> libsdl1.2debian i386 1.2.15+
> kB]
>
> 取得:8 http://
> i386 1:4.4.6-1 [16.0
> kB]
>
> 取得:9 http://
> common i386 3.6.0-2ubuntu2 [5,338
> B]
>
> 取得:10 http://
> i386 3.6.0-2ubuntu2 [130
> kB]
>
> 取得:11 http://
> libcamd2.4.1 i386 1:4.4.6-1 [13.7
> kB]
>
> 取得:12 http://
> libccolamd2.9.1 i386 1:4.4.6-1 [15.0
> kB]
>
> 取得:13 http://
> libgfortran3 i386 5.4.0-6ubuntu1~
> kB]
>
> 取得:14 http://
> i386 3.6.0-2ubuntu2 [1,764
> kB]
>
> 取得:15 http://
> libcholmod3.0.6 i386 1:4.4.6-1 [208
> kB]
>
> 取得:16 http://
> libumfpack5.7.1 i386 1:4.4.6-1 [132
> kB]
>
> 取得:17 http://
> libgegl-0.3-0 i386 0.3.4-1ubuntu2 [1,062
> kB]
>
> 取得:18 http://
> i386 gimp i386 2.8.16-1ubuntu1.1 [3,624
> kB]
>
> 取得:19 http://
> common all 0.999-3ubuntu1 [1,385
> kB]
>
> 取得:20 http://
> i386 0.999-3ubuntu1 [296
> kB]
>
> 18.7 MB を 8秒 で取得しました (2,126
> kB/s)
>
>
> 以前に未選択のパッケージ libgimp2.0 を選択しています。
> (データベースを読み込んでいます ... 現在 221575 個のファイルとディレクトリがイ
> .../libgimp2.
> libgimp2.0 (2.8.16-1ubuntu1.1) を展開しています...
> 以前に未選択のパッケージ gimp-data を選択しています。
> .../gimp-
> gimp-data (2.8.16-1ubuntu1.1) を展開しています...
> 以前に未選択のパッケージ python-cairo を選択しています。
> .../python-
> python-cairo (1.8.8-2) を展開しています...
> 以前に未選択のパッケージ python-gobject-2 を選択しています。
> .../python-
> python-gobject-2 (2.28.6-12ubuntu1) を展開しています...
> 以前に未選択のパッケージ python-gtk2 を選択しています。
> .../python-
> python-gtk2 (2.24.0-4ubuntu1) を展開しています...
> 以前に未選択のパッケージ libbabl-0.1-0:i386 を選択しています。
> .../libbabl-
> libbabl-0.1-0:i386 (0.1.16-1) を展開しています...
> 以前に未選択のパッケージ libsdl1.
> .../libsdl1.
> ...
> libsdl1.
> 以前に未選択のパッケージ libamd2.4.1:i386 を選択しています。
> .../libamd2.
> libamd2.4.1:i386 (1:4.4.6-1) を展開しています...
> 以前に未選択のパッケージ libblas-common を選択しています。
> .../libblas-
> libblas-common (3.6.0-2ubuntu2) を展開しています...
> 以前に未選択のパッケージ libblas3 を選択しています。
> .../libblas3_
> libblas3 (3.6.0-2ubuntu2) を展開しています...
> 以前に未選択のパッケージ libcamd2.4.1:i386 を選択しています。
> .../libcamd2.
> libcamd2.4.1:i386 (1:4.4.6-1) を展開しています...
> 以前に未選択のパッケージ libccolamd2.
> .../libccolamd2
> libccolamd2.
> 以前に未選択のパッケージ libgfortran3:i386 を選択しています。
> .../libgfortran
> libgfortran3:i386 (5.4.0-
> 以前に未選択のパッケージ liblapack3 を選択しています。
> .../liblapack3_
> liblapack3 (3.6.0-2ubuntu2) を展開しています...
> 以前に未選択のパッケージ libcholmod3.
> .../libcholmod3
> libcholmod3.
> 以前に未選択のパッケージ libumfpack5.
> .../libumfpack5
> libumfpack5.
> 以前に未選択のパッケージ libgegl-0.3-0:i386 を選択しています。
> .../libgegl-
> libgegl-0.3-0:i386 (0.3.4-1ubuntu2) を展開しています...
> 以前に未選択のパッケージ gimp を選択しています。
> .../gimp_
> gimp (2.8.16-1ubuntu1.1) を展開しています...
> 以前に未選択のパッケージ xsane-common を選択しています。
> .../xsane-
> xsane-common (0.999-3ubuntu1) を展開しています...
> 以前に未選択のパッケージ xsane を選択しています。
> .../xsane_
> xsane (0.999-3ubuntu1) を展開しています...
> libc-bin (2.23-0ubuntu11.3) のトリガを処理しています ...
> hicolor-icon-theme (0.15-0ubuntu1.1) のトリガを処理しています ...
> man-db (2.7.5-1) のトリガを処理しています ...
> bamfdaemon (0.5.3~
> Rebuilding /usr/share/
> desktop-file-utils (0.22-1ubuntu5.2) のトリガを処理しています ...
> gnome-menus (3.13.3-6ubuntu3.1) のトリガを処理しています ...
> mime-support (3.59ubuntu1) のトリガを処理しています ...
> doc-base (0.10.7) のトリガを処理しています ...
> doc-base ファイルを 1 個追加 を処理中...
> libgimp2.0 (2.8.16-1ubuntu1.1) を設定しています ...
> gimp-data (2.8.16-1ubuntu1.1) を設定しています ...
> python-cairo (1.8.8-2) を設定しています ...
> python-gobject-2 (2.28.6-12ubuntu1) を設定しています ...
> python-gtk2 (2.24.0-4ubuntu1) を設定しています ...
> libbabl-0.1-0:i386 (0.1.16-1) を設定しています ...
> libsdl1.
> libamd2.4.1:i386 (1:4.4.6-1) を設定しています ...
> libblas-common (3.6.0-2ubuntu2) を設定しています ...
> libblas3 (3.6.0-2ubuntu2) を設定しています ...
> update-
> を提供するために自動モードで /usr/lib/
> libcamd2.4.1:i386 (1:4.4.6-1) を設定しています ...
> libccolamd2.
> libgfortran3:i386 (5.4.0-
> liblapack3 (3.6.0-2ubuntu2) を設定しています ...
> update-
> を提供するために自動モードで /usr/lib/
> libcholmod3.
> libumfpack5.
> libgegl-0.3-0:i386 (0.3.4-1ubuntu2) を設定しています ...
> gimp (2.8.16-1ubuntu1.1) を設定しています ...
> xsane-common (0.999-3ubuntu1) を設定しています ...
> xsane (0.999-3ubuntu1) を設定しています ...
> libc-bin (2.23-0ubuntu11.3) のトリガを処理しています ...
> abunaijiji@
>
>
> From this above long output the question what should i do?
>
> Thank you for your help.
>
>
>
> 2022-04-14 (Thu) の 19:45 +0000 に Manfred Hampl さんは書きました:
> > Your question #701288 on Ubuntu changed:
> > https:/
> >
> > Status: Open => Answered
> >
> > Manfred Hampl proposed the following answer:
> > I asked for the output of the command "sane-find-
> > executed the command "xsane-
> > exist.
> >
> > And I asked you to run "xsane", but you executed "dpkg -l | grep
> > xsane".
> > That is not the same.
> >
|
Revision history for this message
|
#13 |
Again:
I asked for the output of the command "sane-find-
$ xsane
Running "Xsane" I could run the scanner and get an image of the
document scanned. However still a problem to save the image gotten.
Please provide details about the problem.
Do you see an error message, or what exactly happens when you try saving the image?
|
Revision history for this message
|
#14 |
2022-04-15 (Fri) の 08:41 +0000 に Manfred Hampl さんは書きました:
> Your question #701288 on Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Again:
>
> I asked for the output of the command "sane-find-
> executed the command "sane-find scanner" (dash sign missing).
>
> $ xsane
> Running "Xsane" I could run the scanner and get an image of the
> document scanned. However still a problem to save the image gotten.
>
> Please provide details about the problem.
> Do you see an error message, or what exactly happens when you try
> saving the image?
>
|
Revision history for this message
|
#15 |
Hi,
Yes about the dash sign. Just when copy/paste I removed it for unknown
reason.
Running the xsane command does the scanning job done.
I don't get any error message; just I did not know where the image was
saved.
i could trace it and now the problem is over.
Thank you for your help indeed.
d
2022-04-15 (Fri) の 08:41 +0000 に Manfred Hampl さんは書きました:
> Your question #701288 on Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Again:
>
> I asked for the output of the command "sane-find-
> executed the command "sane-find scanner" (dash sign missing).
>
> $ xsane
> Running "Xsane" I could run the scanner and get an image of the
> document scanned. However still a problem to save the image gotten.
>
> Please provide details about the problem.
> Do you see an error message, or what exactly happens when you try
> saving the image?
>
|
Revision history for this message
|
#16 |
If the problem has been resolved, then please set the status of this question document to "solved", e.g. by visiting https:/
|
Revision history for this message
|
#17 |
Thanks Manfred Hampl, that solved my question.
|
Revision history for this message
|
#18 |
Hi,Coming back to your here below answer.What do you mean by "This
requires a complete new installation"?How to proceed?
Thank you.
2022-04-14 (木) の 20:01 +0000 に Manfred Hampl さんは書きました:
> Your question #701288 on Ubuntu changed:
> https:/
> Manfred Hampl posted a new comment:Yes, "CPU 操作モード: 32-bit, 64-bit"
> tells that your CPU is capable of running 64bit operating
> systems.
> 64bit system. This requires a complete new installation.
>
|
Revision history for this message
|
#19 |
There is no supported procedure to directly convert a 32bit version of Ubuntu into a 64bit version.
What you have to do is:
- Create backup copies of all your files that you want to keep to a separate storage medium.
- Do a new installation of Ubuntu from a 64bit installation medium, overwriting your previous Ubuntu installation (this will delete all files).
- Restore your private files from the backup medium.
|
Revision history for this message
|
#20 |
Thank you.
Will do so.
2022-04-18 (月) の 07:01 +0000 に Manfred Hampl さんは書きました:
> Your question #701288 on Ubuntu changed:
> https:/
>
> Manfred Hampl posted a new comment:
> There is no supported procedure to directly convert a 32bit version of Ubuntu into a 64bit version.
> What you have to do is:
> - Create backup copies of all your files that you want to keep to a separate storage medium.
> - Do a new installation of Ubuntu from a 64bit installation medium, overwriting your previous Ubuntu installation (this will delete all files).
> - Restore your private files from the backup medium.
>
>
|
Revision history for this message
|
#21 |
Hi, Booting issue.1/ DVD made for the boot of ubuntu-
amd64.iso using the procedure UbuntuでISOイメージを
https:/
All data saved on external HD.3/Shutdown4/ Start up and using F12
emulated the Boot on DVD/CD in the BIOS5/ Insert the DVD 7/ The system
did not boot under the DVD but using instead the HDD built in.8/ Did
several times but no way.9/ Boot diagnostic using Boot repair tool:
boot-repair-
No idea how to proceed.Thank you.
boot-repair-
4ppa200 [20220421_1451]
=======
=======
=> Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at
sector 1 of
the same hard drive for core.img. core.img is at this location and
looks
for (,msdos1)
modules
---
--------
fshelp ext2 part_msdos biosdisk
---
--------
sda1:
_______
___
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 18.04.6 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab
/etc/default/grub
sda2:
_______
___
File system: Extended Partition
Boot sector type: Unknown
Boot sector info:
sda5:
_______
___
File system: swap
Boot sector type: -
Boot sector info:
=======
=======
OS#1: 使用しているOS - Ubuntu 18.04.6 LTS CurrentSession on sda1
=======
=======
CPU architecture: 64-bit
Video: Mobile 4 Series Chipset Integrated Graphics Controller Mobile 4
Series Chipset Integrated Graphics Controller from Intel Corporation
Intel Corporation
BOOT_IMAGE of the installed session in use:
/boot/vmlinuz-
9b95f3965556 ro quiet splash vt.handoff=1
df -Th / : /dev/sda1 ext4 363G 14G 332G 4% /
=======
=======
BIOS/UEFI firmware: V1.30 from TOSHIBA
This installed-session is in Legacy/BIOS/CSM mode (not in EFI mode).
=======
=======
Disks info:
_______
sda : notGPT, no-BIOSboot, has-noESP, not-usb,
not-mmc, has-os, no-wind, 2048 sectors * 512 bytes
Partitions info (1/3):
_______
sda1 : is-os, 32, apt-get, grub-pc , grub2, grub-
install, grubenv-ok, update-grub, farbios
Partitions info (2/3):
_______
sda1 : isnotESP, fstab-without-efi, no-nt, no-winload,
no-recov-nor-hid, no-bmgr, notwinboot
Partitions info (3/3):
_______
sda1 : not--sepboot, with-boot, fstab-without-boot, not-
sep-usr, with--usr, fstab-without-usr, std-grub.d,
sda
fdisk -l (filtered):
_______
Disk sda: 372.6 GiB, 400088457216 bytes, 781422768 sectors
Disk identifier: 0x04e5cf96
Boot Start End Sectors Size Id Type
sda1 * 2048 773310463 773308416 368.8G 83 Linux
sda2 773312510 781422591 8110082 3.9G 5 Extended
sda5 773312512 781422591 8110080 3.9G 82 Linux swap / Solaris
parted -lm (filtered):
_______
sda:400GB:
1:1049kB:
2:396GB:
5:396GB:
blkid (filtered):
_______
NAME FSTYPE UUID PARTUUID
sda
├─sda1 ext4 51cbc6c0-
01
├─sda2 04e5cf96-
02
└─sda5 swap cb56adfd-
05
Mount points (filtered):
_______
Avail Use% Mounted on
/dev/sda1 331G 4% /
Mount options (filtered):
_______
/dev/sda1 ext4 rw,relatime,
=======
=======
Ubuntu 51cbc6c0-
Ubuntu, with Linux 4.15.0-176-generic 51cbc6c0-
9b95f3965556
Ubuntu, with Linux 4.15.0-175-generic 51cbc6c0-
9b95f3965556
Ubuntu, with Linux 4.15.0-142-generic 51cbc6c0-
9b95f3965556
### END /etc/grub.
### END /etc/grub.
=======
=======
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=51cbc6c0-
/ ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=cb56adfd-
none swap sw 0 0
=======
=======
GRUB_DEFAULT=0
GRUB_TIMEOUT_
GRUB_TIMEOUT=10
GRUB_DISTRIBUTO
GRUB_CMDLINE_
GRUB_CMDLINE_
=======
=======
GiB -
GB File Fragment(s)
52.189388275 =
56.037928960 boot/grub/grub.cfg 1
134.638778687 = 144.567287808 boot/grub/i386-
pc/core.img 1
132.836254120 = 142.631841792 boot/vmlinuz-
generic 1
132.672218323 = 142.455709696 boot/vmlinuz-
generic 1
5.180030823 = 5.562015744 boot/vmlinuz-
generic 1
5.180030823 =
5.562015744 vmlinuz 1
132.672218323 =
142.455709696 vmlinuz.old 1
125.083778381 = 134.307684352 boot/initrd.
generic 3
125.052555084 = 134.274158592 boot/initrd.
generic 4
7.279113770 = 7.815888896 boot/initrd.
generic 6
7.279113770 =
7.815888896 initrd.img 6
125.052555084 =
134.274158592 initrd.img.old 4
=======
=======
-rwxr-xr-x 1 root root 12808 Feb 25 2021 10_linux
-rwxr-xr-x 1 root root 11298 Feb 25 2021 20_linux_xen
-rwxr-xr-x 1 root root 12059 Feb 25 2021 30_os-prober
-rwxr-xr-x 1 root root 1418 Jun 21 2017 30_uefi-firmware
-rwxr-xr-x 1 root root 214 Jun 21 2017 40_custom
-rwxr-xr-x 1 root root 216 Jun 21 2017 41_custom
=======
=======
Unknown BootLoader on sda2
00000000 0c 96 f4 ea c9 bd 7f 94 83 02 d3 85 00 02 5e
00 |..............^.|
00000010 00 00 00 0a 20 23 00 00 2d b3 00 00 01 00 5d 14 |.... #..-
.....].|
00000020 23 00 e9 f7 ef 16 65 96 16 f6 2c 18 69 64 91
92 |#.....e...,.id..|
00000030 a5 b6 26 49 6a a5 e2 0e 5d cb b4 8b de 4e 4e
2c |..&Ij...]....NN,|
00000040 ed b3 15 64 82 cb 16 41 97 82 48 2b d6 54 bd
b3 |...d...A..H+.T..|
00000050 94 50 84 02 a2 c5 b6 c5 b6 a5 ae d9 2d 5f 82
a8 |.P..........-_..|
00000060 94 d6 d2 ff 2d 8b 21 c2 05 80 77 1b 9e d6 48 ed |....-
.!...w...H.|
00000070 bc 48 23 84 b0 16 39 fe b2 2c 8b 74 44 a8 78
84 |.H#...9..,.tD.x.|
00000080 9f 79 66 90 a7 2c 82 5e cb 00 6b 39 2d a9 09
2e |.yf..,.^..k9-...|
00000090 b4 5d 54 51 2d 89 7b cb 51 7e 71 61 62 c1 70 4e |.]TQ-
.{.Q~qab.pN|
000000a0 f3 b7 c8 57 4c 54 93 ae a8 79 1d 54 2f 04 85
0e |...WLT...y.T/...|
000000b0 94 15 37 fc 29 60 21 62 c0 02 4b a4 ca 84 05
b6 |..7.)`!b..K.....|
000000c0 54 c2 60 b6 d9 c9 f5 0e c1 64 b7 8c 2a a9 67
1b |T.`......d..*.g.|
000000d0 a5 95 53 a5 9d 93 a5 b0 8b da ec f2 e9 ca 85
22 |..S............"|
000000e0 6c 22 db db d9 67 64 74 94 2f c9 24 70 44 bb
b7 |l"...gdt./.$pD..|
000000f0 92 b8 b2 51 cf e5 80 1d fa 55 a9 33 e5 1d 4a
16 |...Q.....U.3..J.|
00000100 48 00 c4 a0 a2 c9 57 b0 20 a1 d0 4a 59 50 92 4e |H.....W.
..JYP.N|
00000110 cb 23 22 a4 5c 05 8b 6a 2f a5 87 2c 9e 5e 11
48 |.#".\..j/..,.^.H|
00000120 84 8e 49 37 28 80 62 2b 90 02 5d 22 72 02 00
29 |..I7(.b+..]"r..)|
00000130 55 21 6f 27 12 ec 38 02 a2 ca ba e7 35 92 73
2c |U!o'..8.....5.s,|
00000140 89 00 c5 95 59 6c 58 1a d1 a8 08 55 88 b0 2a
d8 |....YlX....U..*.|
00000150 05 a9 6c 03 91 61 34 b8 2a 0d d8 78 01 65 01
d0 |..l..a4.*..x.e..|
00000160 06 94 04 00 40 0c 59 4b d0 6d 48 42 79 c1 0b
a5 |....@.YK.mHBy...|
00000170 2e 12 4d 56 21 25 b4 12 99 e9 e5 e5 96 a5 06
a1 |..MV!%..........|
00000180 55 2e 2d 54 14 00 1c b4 b4 ab c9 3c 76 5c aa a8 |U.-
T.......<v\..|
00000190 44 2a e0 ec 85 2d 9d 8b 4a 16 51 62 84 b6 9e 2d |D*...-
..J.Qb...-|
000001a0 5b 37 7a 8a a9 10 4a 5b 82 81 16 04 00 1d 00
14 |[7z...J[........|
000001b0 28 10 c4 98 b6 e5 bc a4 90 59 41 0c 92 05 00
fe |(........YA.....|
000001c0 ff ff 82 fe ff ff 02 00 00 00 00 c0 7b 00 00
00 |............{...|
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55
aa |..............U.|
00000200
Suggested repair:
_______
The default repair of the Boot-Repair utility would reinstall the grub2
of
sda1 into the MBR of sda.
Grub-efi would not be selected by default because no ESP detected.
Additional repair would be performed: unhide-bootmenu-10s
2022-04-18 (月) の 07:45 +0000 に NOBRUOB さんは書きました:
> Your question #701288 on Ubuntu changed:
> https:/
> NOBRUOB posted a new comment:Thank you.Will do so.
>
> 2022-04-18 (月) の 07:01 +0000 に Manfred Hampl さんは書きました:Your question
> #701288 on Ubuntu changed:
> https:/
> Manfred Hampl posted a new comment:There is no supported procedure to
> directly convert a 32bit version of Ubuntu into a 64bit version.What
> you have to do is:- Create backup copies of all your files that you
> want to keep to a separate storage medium.- Do a new installation of
> Ubuntu from a 64bit installation medium, overwriting your previous
> Ubuntu installation (this will delete all files).- Restore your
> private files from the backup medium.
>
>
>
|
Revision history for this message
|
#22 |
1. The data in your comment #21 are rather unreadable due to line breaks.
2. This has nothing to do with installing a Canon CanoScan LiDE 220 scanner.
Please create a new question about the installation problem and close this one.
|
Revision history for this message
|
#23 |
Could change the BIOS setup for a boot from CD/DV
successfully.
Ubuntu 20:04.Set up done for the Canon IJ printer Canon TR9530Set up
for Scanner using XsaneInstallation of a side monitor display I-O Data
Device Inc 24"
All the problems solved,
Thank you for your help.
Ab Unai JJ
On 木, 2022-04-21 at 06:20 +0000, NOBRUOB wrote:
> Your question #701288 on Ubuntu changed:
> https:/
>
> NOBRUOB posted a new comment:Hi, Booting issue.1/ DVD made for the
> boot of ubuntu-
> procedure UbuntuでISOイメージを
> https:/
> All data saved on external HD.3/Shutdown4/ Start up and using
> F12emulated the Boot on DVD/CD in the BIOS5/ Insert the DVD 7/ The
> systemdid not boot under the DVD but using instead the HDD built
> in.8/ Didseveral times but no way.9/ Boot diagnostic using Boot
> repair tool:boot-
> diagnosticNo idea how to proceed.Thank you.
> boot-repair-
> 4ppa200 [20220421_1451]
> =======
> Summary=
> => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks
> atsector 1 of the same hard drive for core.img. core.img is at
> this location andlooks for (,msdos1)
> following components: modules -------
> -------
> part_msdos biosdisk -------
> -------
> sda1:__
> __________
> File system: ext4 Boot sector type: - Boot sector
> info: Operating System: Ubuntu 18.04.6 LTS Boot
> files: /boot/grub/grub.cfg
> /etc/fstab/
> pc/core.img
> sda2:__
> __________
> File system: Extended Partition Boot sector
> type: Unknown Boot sector info:
> sda5:__
> __________
> File system: swap Boot sector type: - Boot sector
> info:
>
> =======
> detected=
> OS#1: 使用しているOS - Ubuntu 18.04.6 LTS CurrentSession on sda1
> =======
> Host/Hardware=
> CPU architecture: 64-bitVideo: Mobile 4 Series Chipset Integrated
> Graphics Controller Mobile 4Series Chipset Integrated Graphics
> Controller from Intel CorporationIntel CorporationBOOT
> installed session in use:/boot/
> root=UUID=
> vt.handoff=1df -Th / : /dev/sda1 ext4 363G 14G 332G 4% /
> =======
> UEFI===
> BIOS/UEFI firmware: V1.30 from TOSHIBAThis installed-session is in
> Legacy/BIOS/CSM mode (not in EFI mode).
>
> =======
> Info===
> Disks
> info:__
> ____
> sda : notGPT, no-BIOSboot, has-noESP, not-usb, not-
> mmc, has-os, no-wind, 2048 sectors * 512 bytes
> Partitions info
> (1/3):_
> sda1 : is-os, 32, apt-get, grub-pc , grub2, grub-install,
> grubenv-ok, update-grub, farbios
> Partitions info
> (2/3):_
> sda1 : isnotESP, fstab-without-efi, no-nt, no-winload,
> no-recov-nor-hid, no-bmgr, notwinboot
> Partitions info
> (3/3):_
> sda1 : not--sepboot, with-boot, fstab-without-boot, not-
> sep-usr, with--usr, fstab-without-usr, std-grub.d,
> sda
> fdisk -l
> (filtered)
> _
> Disk sda: 372.6 GiB, 400088457216 bytes, 781422768 sectorsDisk
> identifier: 0x04e5cf96 Boot Start End Sectors Size
> Id Typesda1 * 2048 773310463 773308416 368.8G 83
> Linuxsda2 773312510 781422591 8110082 3.9G 5
> Extendedsda5 773312512 781422591 8110080 3.9G 82 Linux swap
> / Solaris
> parted -lm
> (filtered)
> sda:400GB:
> MK4058GS:
> 96GB:400GB:
> blkid
> (filtered)
> ____
> NAME FSTYPE UUID PARTUUID
> LABEL
> PARTLABELsda
> ├─sda1 ext4 51cbc6c0-f27a-
> 4d0f-b663-
> 01 ├─sda2
> 04e5cf96-02 └─sda5
> swap cb56adfd-
> 05
> Mount points
> (filtered)
> Avail Use% Mounted on/dev/sda1 331G 4% /
> Mount options
> (filtered)
> /dev/sda1 ext4 rw,relatime,
> ro,data=ordered
> =======
> (filtered)
> Ubuntu 51cbc6c0-
> 4.15.0-176-generic 51cbc6c0-
> Linux 4.15.0-175-generic 51cbc6c0-
> 9b95f3965556Ubuntu, with Linux 4.15.0-142-generic 51cbc6c0-f27a-
> 4d0f-b663-
> /etc/grub.
> =======
> (filtered)
> # <file system> <mount
> point> <type> <options> <dump> <pass># / was on /dev/sda1
> during installationUUI
> 9b95f3965556/ ext4 errors=remount-ro 0 1# swap
> was on /dev/sda5 during installationUUI
> b56d98ea0b24none swap sw 0 0
> =======
> (filtered)
> GRUB_DEFAULT=
> R=`lsb_release -i -s 2> /dev/null || echo
> Debian`
> =======
> Grub===
> GiB
> -GB File Fragment(s) 52.
> 189388275
> =56.037928960 boot/grub/grub.cfg 1
> 134.638778687 = 144.567287808 boot/grub/i386-
> pc/core.img 1 132.836254120 =
> 142.631841792 boot/vmlinuz-
> 132.672218323 = 142.455709696 boot/vmlinuz-
> generic 1 5.180030823 = 5.562015744 boot/vmlinuz-
> 4.15.0-176-generic 1 5.180030823
> =5.562015744 vmlinuz 1
> 132.672218323
> =142.455709696 vmlinuz.old 1
> 125.083778381 = 134.307684352 boot/initrd.
> generic 3 125.052555084 = 134.274158592 boot/initrd.img-
> 4.15.0-175-generic 4 7.279113770 =
> 7.815888896 boot/initrd.
> generic 6 7.279113770
> =7.815888896 initrd.img 6
> 125.052555084
> =134.274158592 initrd.img.old 4
> =======
> (filtered)
> -rwxr-xr-x 1 root root 12808 Feb 25 2021 10_linux-rwxr-xr-x 1 root
> root 11298 Feb 25 2021 20_linux_
> 25 2021 30_os-prober-
> 30_uefi-
> rwxr-xr-x 1 root root 216 Jun 21 2017 41_custom
> =======
> Sectors/
> Unknown BootLoader on sda2
> 00000000 0c 96 f4 ea c9 bd 7f 94 83 02 d3 85 00 02
> 5e00 |......
> 00 01 00 5d 14 |.... #..-...
> 96 16 f6 2c 18 69 64 9192 |#.....
> 6a a5 e2 0e 5d cb b4 8b de 4e 4e2c |..&Ij.
> b3 15 64 82 cb 16 41 97 82 48 2b d6 54
> bdb3 |...d..
> d9 2d 5f 82a8 |.P....
> c2 05 80 77 1b 9e d6 48 ed |....-.
> b0 16 39 fe b2 2c 8b 74 44 a8 7884 |.H#...
> 79 66 90 a7 2c 82 5e cb 00 6b 39 2d a9 092e |.yf..,.^..k9-
> ...|00000090 b4 5d 54 51 2d 89 7b cb 51 7e 71 61 62 c1 70
> 4e |.]TQ-.
> 2f 04 850e |...WLT.
> 02 4b a4 ca 84 05b6 |..7.)`
> 0e c1 64 b7 8c 2a a9 671b |T.`...
> 9d 93 a5 b0 8b da ec f2 e9 ca 8522 |..S...
> 22 db db d9 67 64 74 94 2f c9 24 70 44
> bbb7 |l"...gdt.
> 33 e5 1d 4a16 |...Q..
> b0 20 a1 d0 4a 59 50 92 4e |H.....
> 5c 05 8b 6a 2f a5 87 2c 9e 5e 1148 |.#".\.
> 8e 49 37 28 80 62 2b 90 02 5d 22 72 02
> 0029 |..I7(.
> e7 35 92 732c |U!o'..
> 1a d1 a8 08 55 88 b0 2ad8 |....YlX.
> 91 61 34 b8 2a 0d d8 78 01 65 01d0 |..l..a4.
> 94 04 00 40 0c 59 4b d0 6d 48 42 79 c1
> 0ba5 |....@.
> e5 96 a5 06a1 |..MV!%
> b4 b4 ab c9 3c 76 5c aa a8 |U.-T..
> 85 2d 9d 8b 4a 16 51 62 84 b6 9e 2d |D*...-
> 37 7a 8a a9 10 4a 5b 82 81 16 04 00 1d
> 0014 |[7z...
> 0c 92 05 00fe |(.....
> 00 00 00 00 c0 7b 00 0000 |......
> 00 00 00 00 00 00 00 00 00 00 0000 |......
> 00 00 00 00 00 00 00 00 00 00 00 00 00
> 55aa |......
>
>
> Suggested
> repair:
> The default repair of the Boot-Repair utility would reinstall the
> grub2ofsda1 into the MBR of sda.Grub-efi would not be selected by
> default because no ESP detected.Additional repair would be performed:
> unhide-bootmenu-10s
>
>
> 2022-04-18 (月) の 07:45 +0000 に NOBRUOB さんは書きました:
> > Your question #701288 on Ubuntu changed:
> > https:/
> > NOBRUOB posted a new comment:Thank you.Will do so.
> > 2022-04-18 (月) の 07:01 +0000 に Manfred Hampl さんは書きました:Your
> > question#701288 on Ubuntu changed:
> > https:/
> > Manfred Hampl posted a new comment:There is no supported procedure
> > todirectly convert a 32bit version of Ubuntu into a 64bit
> > version.Whatyou have to do is:- Create backup copies of all your
> > files that youwant to keep to a separate storage medium.- Do a new
> > installation ofUbuntu from a 64bit installation medium, overwriting
> > your previousUbuntu installation (this will delete all files).-
> > Restore yourprivate files from the backup medium.
> >
> >
