From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: scanner problem : latest
Date: Fri, 20 Jul 2018 09:04:26 -0400 [thread overview]
Message-ID: <20180720130426.GA1967@ca.inter.net> (raw)
In-Reply-To: <20180719160843.ik3sjhcwt4z7gswm@matica.foolinux.mooo.com>
180719 Ian Zimmerman wrote:
> On 2018-07-19 05:29, Philip Webb wrote:
>> The Mint version seems to find a file in /usr/share/iscan-data ,
>> which the others don't find, but that file is present in my Gentoo system.
> I have not looked at the strace log, but this smacks of permissions
> and possibly Selinux, if you've let that beast loose.
I checked the permissions for iscan-data & they seem ok.
No, I've never tried to use Selinux.
However, I've just escaped fr another beast, ie Linux Mint 19 :
DON'T try to install it alongside Gentoo !!
This beast leads you along to a point where you've told it where to install
-- a partition on my HDD (sdb5) -- ,
you click 'proceed' & it chugs along nicely for some time,
then it says it's trying to install a bootloader
without asking whether you want it to or where to do it.
Next, it says it's failed to install Grub -- which I've never used -- ,
offers several ugly-looking options & freezes.
All you can do is a hard power-off & when you restart,
instead of the regular Lilo box of options, there's only a Grub prompt.
Disaster looks you in the face !
SystemRescue to the rescue : Gentoo /boot is unaltered,
so copy lilo.conf into the SR /etc dir, edit it to use SR paths,
mount the Gentoo /boot , run 'lilo' & the MBR is restored to what it sb.
Reboot & the familiar Lilo screen appears !
I wanted to see whether the latest Mint found my scanner,
which would suggest that the problem doesn't involve the kernel, at least.
I'm not trying again !
On inspection, Mint 19 does seem to have installed itself on /dev/sdb5 ,
so I can copy the vital files from its /boot to my own Gentoo /boot ,
edit lilo.conf accordingly & see if it will start : not today !
Next up -- too late for today -- is to see if I can get Nvidia working
with an earlier kernel : at present it isn't.
Then I can find out if Xsane can find my scanner with another kernel.
Can anyone take a look at my Strace output ( 3 files),
which is at http://chass.utoronto.ca/~purslow/test ?
That would be a real help.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next prev parent reply other threads:[~2018-07-20 13:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 6:38 [gentoo-user] scanner problem Philip Webb
2018-07-17 14:18 ` Steven Lembark
2018-07-17 14:23 ` Jack
2018-07-17 14:43 ` Mick
2018-07-18 8:16 ` Philip Webb
2018-07-18 9:50 ` Andrew Udvare
2018-07-19 6:03 ` Raffaele Belardi
2018-07-19 9:29 ` [gentoo-user] scanner problem : latest Philip Webb
2018-07-19 10:03 ` Mick
2018-07-19 16:08 ` [gentoo-user] " Ian Zimmerman
2018-07-20 13:04 ` Philip Webb [this message]
2018-07-20 13:25 ` [gentoo-user] Re: scanner problem : PS Philip Webb
2018-07-20 22:10 ` [gentoo-user] Re: scanner problem : latest Mick
2018-07-23 22:29 ` Neil Bothwick
2018-07-24 14:14 ` Philip Webb
2018-07-24 14:38 ` Mick
2018-07-26 14:30 ` Mick
2018-07-24 20:10 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180720130426.GA1967@ca.inter.net \
--to=purslow@ca.inter.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox