SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Open the file in Gimp, and go to Image -> Mode -> Indexed. Now under "Generate Optimum Palette" choose the maximum number of colors to be 255 (Well, I chose 255. Dunno how selecting a different number will affect this. I'm no graphics guru ). Click "Convert" and save. I think that should do it.
Now, the slack.dat file details the dimensional, positional and color parameters of the image (if I'm not wrong). Keep this file open alongside for reference when you are editing the variables. I'm sure it'll help.
ok cool, so gonna sound dumb again just reading through it, will this work with any image, i.e. how do i know how many columns, row etc will i need or is it just a case of hit an miss
ok cool, so gonna sound dumb again just reading through it, will this work with any image, i.e. how do i know how many columns, row etc will i need or is it just a case of hit an miss
Ok, that output was generated when I used this image. Of course, I scaled it down, and converted it. Using those same variable values on your image might not produce the desired result ( I tried it on my image, and it got spliced). So yes, it is a bit of trial and error, unless you are an expert in graphics. But please don't get exasperated now that you've gotten this far. Also, if you haven't visited the link that aocab provided, I suggest you do. I got all the info that I'm now disseminating from that link.
ah the command is /sbin/lilo -E FILENAME* but now it give me some options to which i am noobishly unsure:
how would i use these options
i went for broke and just write then yes for the next two questions and it still returns with "fatal unsupported bitmap", if there are any gimp masters (wow that sounds a lil wierd) that could give me info an how to make it supported with gimp that may make this easier,
i know some of you could prob do it for me but thats not the point i need to learn lol
thanks again in advance
Quote:
3) you can use lilo.conf or the bmp file itself to tell lilo the color information (for your text and timer-box)
Using /sbin/lilo -E FILENAME sets the color information in the bmp file.
I did not use that method.
I modified lilo.conf to set the color information.
Code:
man lilo.conf
has all the details on how to set the various settings (and was a little easier for me to understand).
Hmm...Something interesting happened after I fed the info into my lilo.conf. I ran lilo, and got this:
Code:
root [ ~ ]# lilo
Warning: LBA32 addressing assumed
Warning: Unable to determine video adapter in use in the present system.
Warning: Video adapter does not support VESA BIOS extensions needed for
display of 256 colors. Boot loader will fall back to TEXT only operation.
Added Slack *
And now there's no bootloader Darn.
Last edited by corbis_demon; 08-21-2010 at 12:10 PM.
Hmm...Something interesting happened after I fed the info into my lilo.conf. I ran lilo, and got this:
Code:
root [ ~ ]# lilo
Warning: LBA32 addressing assumed
Warning: Unable to determine video adapter in use in the present system.
Warning: Video adapter does not support VESA BIOS extensions needed for
display of 256 colors. Boot loader will fall back to TEXT only operation.
Added Slack *
And now there's no bootloader Darn.
You should still have a bootloader (those are just warnings)...?
I've gotten those messages before when I had to chroot into the system to run lilo when something went wrong. I would just re-run lilo again as root once I could get back into the system in runlevel 3.
Sorry, I made a typo in the .conf . root got assigned to a non-existent boot image. . But yes, you're right, those are just warnings. But the interesting bit is that no warnings (other than the LB32 one) were issued when I ran the command from inside a chroot. Not important, I'm sure. Sorry to bother. Thanks for taking time out to reply.
EDIT: Really sorry to take the discussion somewhat off the track, but kernel 2.6.35.2 seems to have got serious bug that's causing boot failures. Is there a fix available in 2.6.35.3? I mean it's a pain recompiling now that I compiled 2.6.35.2 a few days back.
Last edited by corbis_demon; 08-21-2010 at 12:51 PM.
Sorry, I made a typo in the .conf . root got assigned to a non-existent boot image. . But yes, you're right, those are just warnings. But the interesting bit is that no warnings (other than the LB32 one) were issued when I ran the command from inside a chroot. Not important, I'm sure. Sorry to bother. Thanks for taking time out to reply.
you can get rid of the lba32 warning by adding "lba32"
(without quotes) to the beginning of lilo.conf.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.