Bug#182704: Debconf configuration sets use_fbdev without asking, making X unstartable
On Fri, Feb 28, 2003 at 01:40:09AM -0500, Branden Robinson <branden@debian.org> was heard to say:
> On Thu, Feb 27, 2003 at 03:48:38PM -0500, Daniel Burrows wrote:
> > On Thu, Feb 27, 2003 at 06:51:02PM +0100, Michel D?nzer <daenzer@debian.org> was heard to say:
> > > Even with dpkg-reconfigure -plow ?
> >
> > I would hope so, since low is my default priority. Anyway, I just
> > checked, and it skips that question even if I explicitly specify "low".
> [...]
> > My, that's messed up..anyway, maybe I should have used the example
> > where I tested [ -n $(cat /proc/fb) ] and it failed. How's this?
> > torrent:~> cat /proc/fb
> > torrent:~> od /proc/fb
> > 0000000
> > torrent:~> cat /proc/fb | wc -c
> > 0
>
> Well, let's have a look at the code, shall we? Shell scripts are not
> rocket science.
>
> # use fbcon kernel functions?
> if [ -e /proc/fb ]; then
> if [ -n "$(cat /proc/fb)" ]; then
> auto_answer db_input high xserver-xfree86/config/device/use_fbdev "true"
> fi
> else
> db_get xserver-xfree86/config/device/use_fbdev || debug_report_status "db_get xserver-xfree86/config/device/use_fbdev" "$?"
> if [ "$RET" = "true" ]; then
> debug_echo "xserver-xfree86/config/device/use_fbdev is \"true\" but /proc/fb does not exist; setting template to \"false\""
> db_set xserver-xfree86/config/device/use_fbdev false
> fi
> fi
>
> Before you jump all over that "auto_answer" thing, hold your horses:
[snip]
It doesn't matter -- what I was trying to say (not very clearly)
earlier is that /proc/fb exists but is empty; thus, all the questions
above are skipped. "auto_answer" never runs.
I think I may have set the option at some point in the past, and now
the script won't let me change it.
*pokes around*
aha. If I manually load the framebuffer driver, then (after I get
control over my console -- seems loading the driver while X is running
is not such a hot idea) X works with "usefbdev", and the config script
gives me the option to disable use of the framebuffer. Oh, and /proc/fb
contains actual data.
Is there a good reason to leave the setting alone if /proc/fb is
empty? AIUI this corresponds to "no available framebuffer devices", and
so silently preserving a pre-existing "true" value doesn't make sense.
(at the least, asking seems like a good idea)
Daniel
--
/-------------------- Daniel Burrows <dburrows@debian.org> -------------------\
| "I've struggled with reality for thirty-five years, |
| but I'm glad to say that I finally won." |
| -- _Harvey_ |
\------- (if (not (understand-this)) (go-to http://www.schemers.org)) --------/
Reply to: