Bug#163392: (NV) EE: Cannot read bios (5)
On Fri, Oct 18, 2002 at 02:01:54PM +0200, José Salavert Torres wrote: > >What do you mean, "nothing"? Using the "fb device driver" renders > >debconf utterly non-functional on your system? > > > >You are asked no questions at all? > > Yes, the problem was that I erased dboostrap_settings from root > directory, then the dpkg-reconfigure program doesn't appeared with > ncurses, after ansvering all the questions it doesn't works. You have me completely confused. "You are asked no questios at all?" "Yes...after answering all the questions, it doesn't work." I cannot reconcile these contradictory statements. Either you were asked questions or you were not. -- G. Branden Robinson| You could wire up a dead rat to a Debian GNU/Linux | DIMM socket and the PC BIOS memory [EMAIL PROTECTED] | test would pass it just fine. http://people.debian.org/~branden/ | -- Ethan Benson pgpRqUpibhmMu.pgp Description: PGP signature
Bug#163392: (NV) EE: Cannot read bios (5)
On Fri, Oct 18, 2002 at 02:01:54PM +0200, José Salavert Torres wrote: > >What do you mean, "nothing"? Using the "fb device driver" renders > >debconf utterly non-functional on your system? > > > >You are asked no questions at all? > > Yes, the problem was that I erased dboostrap_settings from root > directory, then the dpkg-reconfigure program doesn't appeared with > ncurses, after ansvering all the questions it doesn't works. You have me completely confused. "You are asked no questios at all?" "Yes...after answering all the questions, it doesn't work." I cannot reconcile these contradictory statements. Either you were asked questions or you were not. -- G. Branden Robinson| You could wire up a dead rat to a Debian GNU/Linux | DIMM socket and the PC BIOS memory [EMAIL PROTECTED] | test would pass it just fine. http://people.debian.org/~branden/ | -- Ethan Benson msg04228/pgp0.pgp Description: PGP signature
Bug#163392: (NV) EE: Cannot read bios (5)
El Miércoles, 16 octubre, 2002, a las 01:26 AM, [EMAIL PROTECTED] escribió: On Tue, Oct 15, 2002 at 11:30:50PM +0200, José Salavert Torres wrote: El Jueves, 3 octubre, 2002, a las 07:24 PM, Branden Robinson escribió: On Thu, Oct 03, 2002 at 02:53:47PM +0200, José Salavert Torres wrote: You should try Debian's configuration method instead. # dpkg-reconfigure xserver-xfree86 When I enter that command nothing happens, only happened at first boot. According to Joey Hess, dpkg-reconfigure implies "-plow". What happens if you run # dpkg-reconfigure -plow xserver-xfree86 Nothing, I've used the fb device driver instead. (kernel 2.4.20) What do you mean, "nothing"? Using the "fb device driver" renders debconf utterly non-functional on your system? You are asked no questions at all? Yes, the problem was that I erased dboostrap_settings from root directory, then the dpkg-reconfigure program doesn't appeared with ncurses, after ansvering all the questions it doesn't works. Then I've compiled a 2.4.20 benhq kernel with Nvidia framebuffer support, and instead of "nv" I've used "fbd" (framebuffer). In order to make this work I had to remove the option "Standard VGA console" (or something like that) in kernel configuration. I'm going to try if with the "nv" driver happens the same thing, but 2.4.20-pre9 has problems (debugger stops startup and network doesn't work) and I have to study a lot, I will wait for a stable release.
Bug#163392: (NV) EE: Cannot read bios (5)
El Miércoles, 16 octubre, 2002, a las 01:26 AM, [EMAIL PROTECTED] escribió: On Tue, Oct 15, 2002 at 11:30:50PM +0200, José Salavert Torres wrote: El Jueves, 3 octubre, 2002, a las 07:24 PM, Branden Robinson escribió: On Thu, Oct 03, 2002 at 02:53:47PM +0200, José Salavert Torres wrote: You should try Debian's configuration method instead. # dpkg-reconfigure xserver-xfree86 When I enter that command nothing happens, only happened at first boot. According to Joey Hess, dpkg-reconfigure implies "-plow". What happens if you run # dpkg-reconfigure -plow xserver-xfree86 Nothing, I've used the fb device driver instead. (kernel 2.4.20) What do you mean, "nothing"? Using the "fb device driver" renders debconf utterly non-functional on your system? You are asked no questions at all? Yes, the problem was that I erased dboostrap_settings from root directory, then the dpkg-reconfigure program doesn't appeared with ncurses, after ansvering all the questions it doesn't works. Then I've compiled a 2.4.20 benhq kernel with Nvidia framebuffer support, and instead of "nv" I've used "fbd" (framebuffer). In order to make this work I had to remove the option "Standard VGA console" (or something like that) in kernel configuration. I'm going to try if with the "nv" driver happens the same thing, but 2.4.20-pre9 has problems (debugger stops startup and network doesn't work) and I have to study a lot, I will wait for a stable release. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163392: (NV) EE: Cannot read bios (5)
On Tue, Oct 15, 2002 at 11:30:50PM +0200, José Salavert Torres wrote: > El Jueves, 3 octubre, 2002, a las 07:24 PM, Branden Robinson escribió: > > >On Thu, Oct 03, 2002 at 02:53:47PM +0200, José Salavert Torres wrote: > >>>You should try Debian's configuration method instead. > >>> > >>># dpkg-reconfigure xserver-xfree86 > >> > >>When I enter that command nothing happens, only happened at first > >>boot. > > > >According to Joey Hess, dpkg-reconfigure implies "-plow". > > > >What happens if you run > > > ># dpkg-reconfigure -plow xserver-xfree86 > > Nothing, I've used the fb device driver instead. (kernel 2.4.20) What do you mean, "nothing"? Using the "fb device driver" renders debconf utterly non-functional on your system? You are asked no questions at all? -- G. Branden Robinson|Somewhere, there is a .sig so funny Debian GNU/Linux |that reading it will cause an [EMAIL PROTECTED] |aneurysm. This is not that .sig. http://people.debian.org/~branden/ | pgpsPg4A1Ly6J.pgp Description: PGP signature
Bug#163392: (NV) EE: Cannot read bios (5)
On Tue, Oct 15, 2002 at 11:30:50PM +0200, José Salavert Torres wrote: > El Jueves, 3 octubre, 2002, a las 07:24 PM, Branden Robinson escribió: > > >On Thu, Oct 03, 2002 at 02:53:47PM +0200, José Salavert Torres wrote: > >>>You should try Debian's configuration method instead. > >>> > >>># dpkg-reconfigure xserver-xfree86 > >> > >>When I enter that command nothing happens, only happened at first > >>boot. > > > >According to Joey Hess, dpkg-reconfigure implies "-plow". > > > >What happens if you run > > > ># dpkg-reconfigure -plow xserver-xfree86 > > Nothing, I've used the fb device driver instead. (kernel 2.4.20) What do you mean, "nothing"? Using the "fb device driver" renders debconf utterly non-functional on your system? You are asked no questions at all? -- G. Branden Robinson|Somewhere, there is a .sig so funny Debian GNU/Linux |that reading it will cause an [EMAIL PROTECTED] |aneurysm. This is not that .sig. http://people.debian.org/~branden/ | msg04186/pgp0.pgp Description: PGP signature
