SEO

#1 (**permalink**) 02-20-2008, 10:02 AM

Just installed Slack 10.2, then tried to replace the 2.4 kernel with
the latest 2.6 (I'm a masochist; I admit it).

I'm hoping it's not *entirely* out of place to ask this here, and I
couldn't find the proper kernel newsgroup, so point me in the right
direction if so, please?

Anyhow.

Compiled in framebuffer, console support, and that for the card in the
system (an old ATI Mach64 GT). Tell LILO to ask, and select an 80x50
mode.

Works - for a second. Kernel boot scrolls by, then... big, blocky
text again. The default 2.4 kernel works perfecly like this, so I'm
somewhat stumped. Any particular options on how to get this working?

Also, is LVM patched into the existing 2.4 kernel in slackware, or am
I missing something? Something's different about 2.4 and 2.6 in this
regard, isn't there? I can't find enough specifics, however.

#2 (**permalink**) 02-20-2008, 10:02 AM

lamerfreak wrote:

> Just installed Slack 10.2, then tried to replace the 2.4 kernel with
> the latest 2.6 (I'm a masochist; I admit it).

No. 2.6.13 is the way to go. The way you describe it, you forgot the
framebuffer fonts. The machine I'm writing this on has a 2.6.12 kernel, but
IIRC, the configuration is the same. Be sure to have the following enabled:

Device drivers -->
Graphics support -->
--- Console display driver support ---[*] Video mode selection support
<*> Framebuffer console support[*] Select compiled-in fonts
...[*] VGA 8x16 fonts

From here, you can play with different fonts. Some remind of the old Atari
days, but the one indicated is most "standard".

Concerning the stanza in LILO, I don't know, since I use GRUB. But you have
to have some 'vga=773' somewhere.

Cheers,

Niki Kovacs
--
I'm not as think as you stoned I am.

#3 (**permalink**) 02-20-2008, 10:02 AM

On Fri, 23 Sep 2005 22:00:39 -0500,
lamerfreak <laaaaameeeeerfreak@namor.ca> wrote:

> Compiled in framebuffer, console support, and that for the card in the
> system (an old ATI Mach64 GT). Tell LILO to ask, and select an 80x50
> mode.

> Works - for a second. Kernel boot scrolls by, then... big, blocky
> text again. The default 2.4 kernel works perfecly like this, so I'm
> somewhat stumped. Any particular options on how to get this working?

I can't help with configuring this particular framebuffer, but if you
can't find a solution, I suggest disabling specific ATI support and
using the VESA framebuffer. Details of doing this are in the following
link, so I won't repeat myself.

<http://wombat.san-francisco.ca.us/faqomatic/cache/92.html>

> Also, is LVM patched into the existing 2.4 kernel in slackware, or am
> I missing something?

Yes. Slackware has LVM support enabled in the kernel and an LVM 1
package.

> Something's different about 2.4 and 2.6 in this
> regard, isn't there?

I haven't tried LVM on 2.6 yet, but my vague understanding is that 2.6
supports LVM 2 only. There is LVM 2 packages along with the 2.6
packages, so I assume the LVM 2 support is enabled. You can check the
kernel's .config to be sure.

--
Mark Hill

#4 (**permalink**) 02-20-2008, 10:03 AM

>> Compiled in framebuffer, console support, and that for the card in the
>> system (an old ATI Mach64 GT). Tell LILO to ask, and select an 80x50
>> mode.
>
>> Works - for a second. Kernel boot scrolls by, then... big, blocky
>> text again. The default 2.4 kernel works perfecly like this, so I'm
>> somewhat stumped. Any particular options on how to get this working?
>
>I can't help with configuring this particular framebuffer, but if you
>can't find a solution, I suggest disabling specific ATI support and
>using the VESA framebuffer. Details of doing this are in the following
>link, so I won't repeat myself.

>
><http://wombat.san-francisco.ca.us/faqomatic/cache/92.html>

Innnnnnnnnnnnnteresting, yes. Hm. The VESA VGA modes are what I want
to get working, I was just under the impression that I needed to
select my specific card, too...

Thanks, I'll be trying this. Never thought of appending the module
within LILO, either, so that's something. Mayhap that lack is what's
causing the switch - boot with kernel option, then switch to the ATI
which isn't specifically set, so... hm.

>> Also, is LVM patched into the existing 2.4 kernel in slackware, or am
>> I missing something?
>
>Yes. Slackware has LVM support enabled in the kernel and an LVM 1
>package.
>
>> Something's different about 2.4 and 2.6 in this
>> regard, isn't there?
>
>I haven't tried LVM on 2.6 yet, but my vague understanding is that 2.6
>supports LVM 2 only. There is LVM 2 packages along with the 2.6
>packages, so I assume the LVM 2 support is enabled. You can check the
>kernel's .config to be sure.

I'm finding scant mention, but the kernel options mention RAID/LVM
together, but no option beneath it for LVM, specifically... but if 2.6
supports LVM2, and the slackware tools support LVM1... then I guess I
might need to re-do them. Perhaps that's why it's complaining...

Thanks, very good tips. It'll occupy a day or so.

#5 (**permalink**) 02-20-2008, 10:03 AM

On Sat, 24 Sep 2005 13:05:00 -0500,
lamerfreak <laaaaameeeeerfreak@namor.ca> wrote:

> I was just under the impression that I needed to
> select my specific card, too...

I've made the same mistake.

> but if 2.6 supports LVM2, and the slackware tools support LVM1...
> then I guess I might need to re-do them. Perhaps that's why it's
> complaining...

Although the LVM1 packages are installed from the main package set,
there are extra LVM2 (and device mapper) packages available in /testing.

--
Mark Hill

#6 (**permalink**) 02-20-2008, 10:03 AM

>> but if 2.6 supports LVM2, and the slackware tools support LVM1...
>> then I guess I might need to re-do them. Perhaps that's why it's
>> complaining...
>
>Although the LVM1 packages are installed from the main package set,
>there are extra LVM2 (and device mapper) packages available in /testing.

Yeah, still reading and trying to make sense.

I'll probably try building the tools for LVM2 with the 2.6 kernel as
long as I'm at it, but I'm looking at software RAID this time,
perhaps. Strangely, it seems *easier* to set up the basics, there.

Two harddrives dead within a week, and coming into 5 more, doesn't
hurt the decision, either.

#7 (**permalink**) 02-20-2008, 10:05 AM

>> I was just under the impression that I needed to
>> select my specific card, too...
>
>I've made the same mistake.

Update: pulled the box apart, reinstalled, re-did the kernel, and...
it works. Flawlessly, so far. Thanks!

Now just to get rid of the SCSI errors on shutdown.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Possible OT: framebuffer?