GRUB4DOS 0.4.4 + Knoppix 6.4.4 boot problems

[Capricorny]

I don't know grub4dos at all, but..
First memory: 3GB is limit with 32-bits. Run Knoppix with the 64-bits option (cheat code knoppix64) and all memory will be reported and used.
Then Knoppix: Are you sure this should work? I think the problem may be in your sequence of commands - what are you really telling the Knoppix bootloader here?
Clearly, the Knoppix boot is searching for a loadable image, and doesn't find any. There is a cheat code for this type of booting, from 6.4.4 cheat code list:

knoppix bootfrom=/dev/sda1/KNX.iso Access image, boot from ISO-Image.

I would have tried setting up an ordinary grub entry, like I give an example of here: http://www.knoppix.net/forum/threads...e-from-scratch
with the bootfrom option used in the kernel line.

[KnUser]

I don't know grub4dos at all, but..
First memory: 3GB is limit with 32-bits. Run Knoppix with the 64-bits option (cheat code knoppix64) and all memory will be reported and used.

Thank you Capricorny, you're right 3GB is a natural 32-bit computing limit (without memory mapping tricks and so, quite time ago I've barely remember to read elsewhere that old Windows server editions had a special memory remapping mode to address more than 3GB but less than 4GB RAM in 32-bit enviroment) your suggestion on the cheat code was very helpful resulting in the following change:

Linux Kernel 2.6.37, 3039 MB RAM ==[TO]==> Linux Kernel 2.6.37-64, 3960 MB RAM
A whopping 921 MB RAM detection and/or usage increase.
Please note that differences are emphasized in underlined bold.

It seems GRUB4DOS 0.4.4, Linux Kernel 2.6.37 (32b) or any other component takes 33 MB RAM in 32-bit mode for booting purposes, 3039MB+33MB==3072MB (3GB) and 136 MB RAM in 64-bit mode, 3960MB+136MB==4096MB (4GB).

I am using my custom 32 bit kernel with Knoppix, it is able to detect the full 4G of memory which I have on my notebook.

Yes kl522, customization is a key factor to do more with less.

One of my next moves with Knoppix 6.4.4 is to modify the ISO to change german.kbd with an old spanish.kbd file so Spanish is loaded witout typing (as in a little-customized by me Knoppix 6.2.1 ISO):

• knoppix lang=es
• knoppix keyboard=es xkeyboard=es

Also I'll study what I did time ago with a Knoppix 6.2.1 ISO because I think it booted the way I wish.

I hope that by customizing/modifying the isolinux boot parameters inside the ISO Knoppix 6.4.4 could be launched from a pendrive/memory card from GRUB4DOS by loading an ISO file because I find very convenient to have a few files in root directory an a directory with a bunch of ISO files that you can fire up from a menu list, I think it is clean and contained.

Again, Thanks All

[kl522]

It seems GRUB4DOS 0.4.4, Linux Kernel 2.6.37 (32b) or any other component takes 33 MB RAM in 32-bit mode for booting purposes, 3039MB+33MB==3072MB (3GB) and 136 MB RAM in 64-bit mode, 3960MB+136MB==4096MB (4GB).

Yes kl522, customization is a key factor to do more with less.

Detecting 3039 MB out of the full 4G memory is ***NOT*** a feature of a 32 bit kernel. As when I compare my kernel config with Klaus Knopper's kernel config, is likely due to the target processor architecture which was chosen. He chose a CONFIG_M486. I happened to have chosen CONFIG_M686. With a non-CONFIG_M486, I have an additional CONFIG_HIMEM64G at my disposal too.

[KnUser]

Detecting 3039 MB out of the full 4G memory is ***NOT*** a feature of a 32 bit kernel. As when I compare my kernel config with Klaus Knopper's kernel config, is likely due to the target processor architecture which was chosen. He chose a CONFIG_M486. I happened to have chosen CONFIG_M686. With a non-CONFIG_M486, I have an additional CONFIG_HIMEM64G at my disposal too.

Dear kl522, your defense of the kernel is commendable but the alleged/veiled attack to the 32-bit kernel from my side is not so (an attack, I mean).

I stated clearly that whatever it be (GRUB4DOS 0.4.4, Linux Kernel 2.6.37 (32b) or any other component) takes 33 MB RAM in 32-bit mode for booting purposes, by the sole calculation of 3072MB-3039MB==33MB. Is not my intention to blame none particulary in a special way. What I mean is that it is mathematically true that 3039 is NOT EQUAL to 3072. Perhaps I find a bit hard to explain myself.

It seems GRUB4DOS 0.4.4, Linux Kernel 2.6.37 (32b) or any other component takes 33 MB RAM in 32-bit mode for booting purposes, 3039MB+33MB==3072MB (3GB) and 136 MB RAM in 64-bit mode, 3960MB+136MB==4096MB (4GB).

Again, thanks kl522.

I'll be a bit busy the next days so I'll try to attend this thread and schedule the aforementioned ISO customizations for a later moment but any ideas/comments relating to the topic of this thread are welcome.

[kl522]

I failed to understand the need to do any calculation.

Sure, when the bootloader such as grub4dos boots up, it needs memory. But when linux kernel takes over, it reclaims all the memory used by any other previous program(s). As a matter of fact as proven on my notebook when I booted using grub4dos, I still have full access to 4G of memory on my 32bit kernel. I don't have more than 4G of memory, otherwise I could even prove that I have access to 64G of memory on my 32bit kernel.