That made a difference, now as it starts to boot it switches VGA mode but I still don't get the graphical frame round the boot messages. I do get the little penguin logo at the start of the boot messages though. Any more ideas ? Thanks Pat

...

...

...

...

"Mark" == Mark Hounschell writes: >> lba32 >> #vga=normal

Mark> Change the line above back to "vga = 791" Even though you Mark> have vga=0x0317 below you still need this I beleive. >> message=/boot/message menu-scheme=Wg:kw:Wg:Wg read-only prompt >> timeout=80 >> # End LILO global Section >> # >> image = /boot/vmlinuz root = /dev/hdc7 label = linux initrd = >> /boot/initrd append="enablepic vga=0x0317" -- ----------------------------------- Pat Colbeck E-mail: pcolbeck@bashq.org Tel: I'm not telling -----------------------------------

On Thursday 06 December 2001 06:27 am, Mads Martin Jørgensen wrote:

* Pat Colbeck [Dec 06. 2001 12:24]:

...

That made a difference, now as it starts to boot it switches VGA mode but I still don't get the graphical frame round the boot messages. I do get the little penguin logo at the start of the boot messages though.

Any more ideas ?

vga=771 is the silly green border translucent tux term. (say that 10 times fast) -- 6:40am up 1:44, 2 users, load average: 0.05, 0.05, 0.01

* Pat Colbeck [Dec 06. 2001 12:57]:

OK I tried vga=771 and vga=0x317 and neither give me the frame. Not a big issue as I have been using linux for about six years without a frame on boot but it is a annoying me as I dont understand why it wont work. One thing has occured to me in that I reinstalled and changed all my partitions to reiserfs except /boot (still ext2) while ago and maybe it stopped workling then. Can the boot process read the graphics off a /usr partition that is reiserfs ?

It does not read the graphics from a partition, it reads it from the initial ramdisk. If you do mk_initrd, you will see it will put in the images for the animations etc. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.

I have the same problem, and it remains after I run mk_initrd and lilo (not forget, what I did initially....) I did not upgrade my system using yast2. So I guess I miss the package or the file that has the graphics and animations. What package is required to get the graphical boot? Op donderdag 6 december 2001 13:02, schreef Mads Martin Jørgensen:

* Pat Colbeck [Dec 06. 2001 12:57]:

...

OK I tried vga=771 and vga=0x317 and neither give me the frame. Not a big issue as I have been using linux for about six years without a frame on boot but it is a annoying me as I dont understand why it wont work. One thing has occured to me in that I reinstalled and changed all my partitions to reiserfs except /boot (still ext2) while ago and maybe it stopped workling then. Can the boot process read the graphics off a /usr partition that is reiserfs ?

It does not read the graphics from a partition, it reads it from the initial ramdisk. If you do mk_initrd, you will see it will put in the images for the animations etc.

-- Richard Bos For those without home the journey is endless

Thanks for the reference to splashanim-0.2-22, it does not seem to be required though. After a cold reboot the graphical login suddenly appeared at one system. At the other I made the message file (/boot/message) myself with mkbootmsg that is in the gfxboot-devel rpm (I hope I remember all the names correctly). The complete procedure is in suse help (support db). This gives me a graphical boot menu. However in SuSE-7.2 the process boot messages were displayed at a graphical screen (it was a pinguin in a white background with a green frame), right now after the graphical menu the system goes back to an ascii alike display, with a pinguin in the left corner. Is this default in suse-7.3 or am I still missing something??? Op vrijdag 7 december 2001 01:50, schreef Konstantin (Kastus) Shchuka:

On Thu, Dec 06, 2001 at 11:14:52PM +0100, Richard Bos wrote:

...

I did not upgrade my system using yast2. So I guess I miss the package or the file that has the graphics and animations. What package is required to get the graphical boot?

splashanim-0.2-22

-Kastus

-- Richard Bos For those without home the journey is endless

Op zaterdag 8 december 2001 01:40, schreef Patrick:

Richard, It probably has something to do with the kernel you are using. I know when I upgraded my kernel on my 7.2pro, I lost Tux on the white & green colorful SuSE bootup screens to the the colorful Tux in the upper left corner. That has been the same with both my Mantel kernel upgrades. Don't know if you have updated your kernel or not or if SuSE has gone to the new graphical bootup that came with the Mantel kernel.

I'm using the certified 2.4.10 SuSE kernel. Okay when it is soemthing that is part of the kernel I do not need to look further then. Thanks for your reply. -- Richard Bos For those without home the journey is endless

Here's a question: how can I change the default runlevel setting in inittab and keep it changed? With SuSE 7.1, it seems, running SuSEconfig changes it back to 5 (at least if you installed as graphical). I want to change to 3 and keep it there, but I don't see any options in rc.config* for setting it so that SuSE knows I want it that way. Thanks, --Jason Van Cleve

It is actually: run yast System Configuration Login Configuration Then select ASCII rather than Graphical Jim 12/07/01 02:55:38 AM, Rene Engelhard wrote:

Jason A.Van Cleve wrote:

...

Here's a question: how can I change the default runlevel setting in inittab and keep it changed? With SuSE 7.1, it seems, running SuSEconfig changes it back to 5 (at least if you installed as graphical). I want to change to 3 and keep it there, but I don't see any options in rc.config* for setting it so that SuSE knows I want it that way.

In YaST 1 you can choose Administration - Login-Configiration (I do not exactly know how it is named in English; I use a german one) but there you can choose ASCII logon and then there will be a ascii logon after the next reboot.

Rene

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com

Thanks, fellows. Using Yast seems to have done the trick. Didn't know about that "ascii" option. As an aside, I don't know how you all feel, but I've always been a little uncertain about Yast1/2 and SuSEconfig, which amount to a layer of abstraction between me and the configuration of my OS. I've considered switching to a more do-it-yourself distro', because I like to know what's going on, and because I want to learn Linux in a fairly "standard" fashion. I wonder if SuSE is very different from other distro's in this respect, or whether anyone else shares my reservation. If there are opinions, I'd be interested. Otherwise, until I get stuck again. . . . --Jason V. C. On Fri, 07 Dec 2001 18:48:58 +0100 Juergen Braukmann wrote:

"Jason A.Van Cleve" schrieb:

...

Here's a question: how can I change the default runlevel setting in inittab and keep it changed? With SuSE 7.1, it seems, running SuSEconfig changes it back to 5 (at least if you installed as graphical). I want to change to 3 and keep it there, but I don't see any options in rc.config* for setting it so that SuSE knows I want it that way.

Thanks,

Hi Jason, You probably activated KDM/XDM in /etc/rc.config.

# # SuSEconfig can do some modifications to /etc/inittab. If you don't want # this, set CHECK_INITTAB to "no". (yes/no) # CHECK_INITTAB="yes"

# # Here you can set the default Display manager (kdm/xdm/gdm/wdm/console). # DISPLAYMANAGER="kdm"

If you set DISPLAYMANAGER to "console" it should stay in level 3. Or, if you set CHECK_INITTAB="no" and change it manually in inittab it won't be overwritten anymore by SuSEconfig.

Juergen

-- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com