Hubert Gabler | 2 Mar 19:30 2007

grml2hd: initrd.img not found

I installed grml 0.9 on a free partition and copied the essential lines
from grml /boot/grub/menu.lst to my standard menu.lst. It reads now:

title		Debian GNU/Linux, kernel 2.6.18-3-486
root		(hd0,2)
kernel		/boot/vmlinuz-2.6.18-3-486 root=/dev/sda3 vga=792 ro 
initrd		/boot/initrd.img-2.6.18-3-486
savedefault

title  		2.6.18-grml
root		(hd1,3)
kernel 		/boot/vmlinuz-2.6.18-grml root=/dev/hdd4 vga=0x0317
initrd 		/boot/initrd.img-2.6.18-grml
savedefault
# boot

title		Windows XP Home
root		(hd0,0)
makeactive
chainloader	+1

Booting grml does not work because the system cannot find
initrd.img-2.6.18-grml. In fact it does not exist in grml's boot file.
Where does it hide ??

(I tried to use initrd.img -2.6.18-3-486, grml starts but I get a lot of
error messages)

Please give me a hint!
Hubert
(Continue reading)

my | 2 Mar 19:51 2007
Picon

bloody raid

Dear M and friends,

Okay, I am trying to accomplish the following and would like a little help, although I realise I should not ask here:

1.  When using debian pure on a partition I can merely chroot /thatpartition and apt-get, install, and so.  I am never able to do this in a grml install, which means that if I want to install grml on partition /blah, I have to be running it in order to work in it, which is a waste of time.

2.  More importantly,  I need fast boot times on the laptops.  I built  kernel no raid, no shit,  in other words, the hardware for the laptop, plus any conceivable thing that one could plug in.  Got rid of every reference in autoconfig and runlevel.conf that I can imagine, and it still seeks the raid array, and, since I had no modules, boot up takes just as long, with the result that the modules are not found.    I want to make it so that there is no reference anywhere to any possible raid issue, and get rid of that ten second lilo delay as well, as I do not need it, since I am always able to boot into grml.  Likewise, most laptops have had no floppy drive for at least two years.  fd0 does not exist, never did, never will, why load the module, or if blacklisted, why seek to seek it? 

Greetings from the wilds of NYC,


Martin


<div>
Dear M and friends,<br><br>
Okay, I am trying to accomplish the following and would like a little help, although I realise I should not ask here:<br><br>
1.&nbsp; When using debian pure on a partition I can merely chroot /thatpartition and apt-get, install, and so.&nbsp; I am never able to do this in a grml install, which means that if I want to install grml on partition /blah, I have to be running it in order to work in it, which is a waste of time.<br><br>
2.&nbsp; More importantly,&nbsp; I need fast boot times on the laptops.&nbsp; I built&nbsp; kernel no raid, no shit,&nbsp; in other words, the hardware for the laptop, plus any conceivable thing that one could plug in.&nbsp; Got rid of every reference in autoconfig and runlevel.conf that I can imagine, and it still seeks the raid array, and, since I had no modules, boot up takes just as long, with the result that the modules are not found.&nbsp;&nbsp;&nbsp; I want to make it so that there is no reference anywhere to any possible raid issue, and get rid of that ten second lilo delay as well, as I do not need it, since I am always able to boot into grml.&nbsp; Likewise, most laptops have had no floppy drive for at least two years.&nbsp; fd0 does not exist, never did, never will, why load the module, or if blacklisted, why seek to seek it?&nbsp; <br><br>
Greetings from the wilds of NYC,<br><br><br>
Martin<br><br><br>
</div>
Michael Prokop | 6 Mar 18:47 2007

Re: grml2hd: initrd.img not found

(Sorry for the delay, chemnitzer linuxdays took my full attention...)

* Hubert Gabler <loipersb <at> aon.at> [20070302 20:15]:

> I installed grml 0.9 on a free partition and copied the essential lines
> from grml /boot/grub/menu.lst to my standard menu.lst. It reads now:

> title		Debian GNU/Linux, kernel 2.6.18-3-486
> root		(hd0,2)
> kernel		/boot/vmlinuz-2.6.18-3-486 root=/dev/sda3 vga=792 ro 
> initrd		/boot/initrd.img-2.6.18-3-486
[...]

Create an initrd if you need it via running:

# update-initramfs -c -t -k $(uname -r)

Adjust your /boot/grub/menu.lst according to your needs and run
'update-grub' then (if you want to :)).

> Booting grml does not work because the system cannot find
> initrd.img-2.6.18-grml. In fact it does not exist in grml's boot file.
> Where does it hide ??

The initrd is not shipped by default with grml 0.9.

But very probably you even do not need an initrd on your system at
all, so just remove the initrd lines in your menu.lst and try
booting then (can be done interactive in grub as well to test it).

regards,
-mika-
-- 
 http://grml.org/            # Linux for texttool-users and sysadmins
 http://wiki.grml.org/       # share your knowledge
 http://grml.supersized.org/ # the grml development weblog
 #grml  <at>  irc.freenode.org    # meet us on irc
(Sorry for the delay, chemnitzer linuxdays took my full attention...)

* Hubert Gabler <loipersb <at> aon.at> [20070302 20:15]:

> I installed grml 0.9 on a free partition and copied the essential lines
> from grml /boot/grub/menu.lst to my standard menu.lst. It reads now:

> title		Debian GNU/Linux, kernel 2.6.18-3-486
> root		(hd0,2)
> kernel		/boot/vmlinuz-2.6.18-3-486 root=/dev/sda3 vga=792 ro 
> initrd		/boot/initrd.img-2.6.18-3-486
[...]

Create an initrd if you need it via running:

# update-initramfs -c -t -k $(uname -r)

Adjust your /boot/grub/menu.lst according to your needs and run
'update-grub' then (if you want to :)).

> Booting grml does not work because the system cannot find
> initrd.img-2.6.18-grml. In fact it does not exist in grml's boot file.
> Where does it hide ??

The initrd is not shipped by default with grml 0.9.

But very probably you even do not need an initrd on your system at
all, so just remove the initrd lines in your menu.lst and try
booting then (can be done interactive in grub as well to test it).

regards,
-mika-
--

-- 
 http://grml.org/            # Linux for texttool-users and sysadmins
 http://wiki.grml.org/       # share your knowledge
 http://grml.supersized.org/ # the grml development weblog
 #grml  <at>  irc.freenode.org    # meet us on irc
Michael Prokop | 6 Mar 18:58 2007

Re: bloody raid

* my <yazdzik <at> nyct.net> [20070302 20:15]:

> 1.  When using debian pure on a partition I can merely
> chroot /thatpartition and apt-get, install, and so.  I am never able to
> do this in a grml install, which means that if I want to install grml on
> partition /blah, I have to be running it in order to work in it, which
> is a waste of time.

Huh?! What does not work when running 'chroot /partition-with-grml-on-it'
and executing something like 'apt-get update' inside then?

> 2.  More importantly,  I need fast boot times on the laptops.  I built
> kernel no raid, no shit,  in other words, the hardware for the laptop,
> plus any conceivable thing that one could plug in.  Got rid of every
> reference in autoconfig and runlevel.conf that I can imagine, and it
> still seeks the raid array, and, since I had no modules, boot up takes
> just as long, with the result that the modules are not found.    I want
> to make it so that there is no reference anywhere to any possible raid
> issue, and get rid of that ten second lilo delay as well, as I do not
> need it, since I am always able to boot into grml.  Likewise, most
> laptops have had no floppy drive for at least two years.  fd0 does not
> exist, never did, never will, why load the module, or if blacklisted,
> why seek to seek it?

Loading this kernel module does not take any noteworthy time. If you
really want to avoid loading of some special kernel modules just run
"blacklist $MODULE" on your grml system and it won't be loaded any
more. Regarding the "why seek to seek the floppy drive": even though
your laptop might not have a floppy *drive* you might have a
connector/connection for it on your motherboard.

To get rid of the raid stuff:

* Deactivate dmraid, mdadm-raid and mdadm in your
  /etc/runlevel.conf. This means it should look like:

  # grep -e mdadm -e dmraid /etc/runlevel.conf
  03      -       -               /etc/init.d/dmraid
  25      -       -               /etc/init.d/mdadm-raid
  25      0,1,6   -               /etc/init.d/mdadm
  50      -       0,6             /etc/init.d/mdadm-raid
  51      -       0,6             /etc/init.d/dmraid

  Notice: there's something related to this on our todolist, see
  http://bts.grml.org/grml/issue89

* Remove the sleep delay in the initrd:

  # apt-get --reinstall install initramfs-tools
  # update-initramfs -c -t -k $(uname -r)
  # lilo                                     # if you use it

  If you do not need the initrd at all just deactivate it in your
  lilo.conf/menu.lst.

regards,
-mika-
-- 
 http://grml.org/            # Linux for texttool-users and sysadmins
 http://wiki.grml.org/       # share your knowledge
 http://grml.supersized.org/ # the grml development weblog
 #grml  <at>  irc.freenode.org    # meet us on irc
* my <yazdzik <at> nyct.net> [20070302 20:15]:

> 1.  When using debian pure on a partition I can merely
> chroot /thatpartition and apt-get, install, and so.  I am never able to
> do this in a grml install, which means that if I want to install grml on
> partition /blah, I have to be running it in order to work in it, which
> is a waste of time.

Huh?! What does not work when running 'chroot /partition-with-grml-on-it'
and executing something like 'apt-get update' inside then?

> 2.  More importantly,  I need fast boot times on the laptops.  I built
> kernel no raid, no shit,  in other words, the hardware for the laptop,
> plus any conceivable thing that one could plug in.  Got rid of every
> reference in autoconfig and runlevel.conf that I can imagine, and it
> still seeks the raid array, and, since I had no modules, boot up takes
> just as long, with the result that the modules are not found.    I want
> to make it so that there is no reference anywhere to any possible raid
> issue, and get rid of that ten second lilo delay as well, as I do not
> need it, since I am always able to boot into grml.  Likewise, most
> laptops have had no floppy drive for at least two years.  fd0 does not
> exist, never did, never will, why load the module, or if blacklisted,
> why seek to seek it?

Loading this kernel module does not take any noteworthy time. If you
really want to avoid loading of some special kernel modules just run
"blacklist $MODULE" on your grml system and it won't be loaded any
more. Regarding the "why seek to seek the floppy drive": even though
your laptop might not have a floppy *drive* you might have a
connector/connection for it on your motherboard.

To get rid of the raid stuff:

* Deactivate dmraid, mdadm-raid and mdadm in your
  /etc/runlevel.conf. This means it should look like:

  # grep -e mdadm -e dmraid /etc/runlevel.conf
  03      -       -               /etc/init.d/dmraid
  25      -       -               /etc/init.d/mdadm-raid
  25      0,1,6   -               /etc/init.d/mdadm
  50      -       0,6             /etc/init.d/mdadm-raid
  51      -       0,6             /etc/init.d/dmraid

  Notice: there's something related to this on our todolist, see
  http://bts.grml.org/grml/issue89

* Remove the sleep delay in the initrd:

  # apt-get --reinstall install initramfs-tools
  # update-initramfs -c -t -k $(uname -r)
  # lilo                                     # if you use it

  If you do not need the initrd at all just deactivate it in your
  lilo.conf/menu.lst.

regards,
-mika-
--

-- 
 http://grml.org/            # Linux for texttool-users and sysadmins
 http://wiki.grml.org/       # share your knowledge
 http://grml.supersized.org/ # the grml development weblog
 #grml  <at>  irc.freenode.org    # meet us on irc
my | 6 Mar 19:59 2007
Picon

Re: bloody raid

Dear Mika,

thanks for you reply when you are so busy - as always, you are the best.

I suspect you know more about everything than I know about anything, and, believe me, your savvy is deeply appreciated.

Funny story, my son's friend, 13, installed ubuntu, hated it, because it was "sissified". (not the word he used )  I gave him a grml cd, told him to ring me if there were any issues.  I never heard from him, so I asked him a week or so later if he needed help.  He said, "nah, it took about twenty minutes to install it, about a half hour to figure how how the f---- to get a gui and I spent a couple of hours installing shit.  It took two or three days to figure out that I needed the ipod aac thing and not the plain ipod, 'cuz hackers are idiots and don't know what people need. They should put ipod as the first thing to do....."

So, you now have the "arrogant teenager TÜV pikerl"
.... apparently, you are cooler than Shuttleworth at the moment. 


Best wishes,

martin


<div>
Dear Mika,<br><br>
thanks for you reply when you are so busy - as always, you are the best.<br><br>
I suspect you know more about everything than I know about anything, and, believe me, your savvy is deeply appreciated.<br><br>
Funny story, my son's friend, 13, installed ubuntu, hated it, because it was "sissified". (not the word he used  )&nbsp; I gave him a grml cd, told him to ring me if there were any issues.&nbsp; I never heard from him, so I asked him a week or so later if he needed help.&nbsp; He said, "nah, it took about twenty minutes to install it, about a half hour to figure how how the f---- to get a gui and I spent a couple of hours installing shit.&nbsp; It took two or three days to figure out that I needed the ipod aac thing and not the plain ipod, 'cuz hackers are idiots and don't know what people need. They should put ipod as the first thing to do....."<br><br>
So, you now have the "arrogant teenager T&Uuml;V pikerl"<br>
.... apparently, you are cooler than Shuttleworth at the moment.&nbsp; <br><br><br>
Best wishes,<br><br>
martin<br><br><br>
</div>
Hubert Gabler | 7 Mar 07:50 2007

grml2hd: more files not found (was initrd.img not found)

Thank you for the hint (initrd), it works now!
Another problem occured, here is the genesis:
boot greml on hd
user: hubert
startx
working on the graphical destop - ok
exit

Now, on the console again, I find a dozen error messages like this:
Can't load /home/grml/.idesktop/icons/xxxx.png bailing --aterm (or--amix
or ... --xterm)
Check to see if the image and path to image is valid

What can I do to make grml find the directory containig the *.png files?
Thank you!
hubert

Michael Prokop | 7 Mar 09:04 2007

Re: grml2hd: more files not found (was initrd.img not found)

* Hubert Gabler <loipersb <at> aon.at> [20070307 08:15]:

[...]

> Now, on the console again, I find a dozen error messages like this:
> Can't load /home/grml/.idesktop/icons/xxxx.png bailing --aterm (or--amix
> or ... --xterm)
> Check to see if the image and path to image is valid

> What can I do to make grml find the directory containig the *.png files?

The reason for this problem are some b0rken apps which don't allow
relative paths for configuration. :( There's a fix inside grml2hd
for this problem but it does not match any setup like in your case.

So to fix the issue just run:

  sed -i "s#/home/grml#/home/$USER#g" /home/$USER/.gkrellm2/user-config
  sed -i "s#/home/grml#/home/$USER#g" /home/$USER/.gkrellm2/theme_config
  sed -i "s#/home/grml#/home/$USER#g" /home/$USER/.idesktop/*.lnk

with $USER set to your username of course. This should fix the issue
with idesktop (and gkrellm2 as well). Run

  grep -r '/home/grml' .*

to locate any further possible problems but there shouldn't be any
further noticeable ones.

regards,
-mika-
-- 
 http://grml.org/            # Linux for texttool-users and sysadmins
 http://wiki.grml.org/       # share your knowledge
 http://grml.supersized.org/ # the grml development weblog
 #grml  <at>  irc.freenode.org    # meet us on irc
* Hubert Gabler <loipersb <at> aon.at> [20070307 08:15]:

[...]

> Now, on the console again, I find a dozen error messages like this:
> Can't load /home/grml/.idesktop/icons/xxxx.png bailing --aterm (or--amix
> or ... --xterm)
> Check to see if the image and path to image is valid

> What can I do to make grml find the directory containig the *.png files?

The reason for this problem are some b0rken apps which don't allow
relative paths for configuration. :( There's a fix inside grml2hd
for this problem but it does not match any setup like in your case.

So to fix the issue just run:

  sed -i "s#/home/grml#/home/$USER#g" /home/$USER/.gkrellm2/user-config
  sed -i "s#/home/grml#/home/$USER#g" /home/$USER/.gkrellm2/theme_config
  sed -i "s#/home/grml#/home/$USER#g" /home/$USER/.idesktop/*.lnk

with $USER set to your username of course. This should fix the issue
with idesktop (and gkrellm2 as well). Run

  grep -r '/home/grml' .*

to locate any further possible problems but there shouldn't be any
further noticeable ones.

regards,
-mika-
--

-- 
 http://grml.org/            # Linux for texttool-users and sysadmins
 http://wiki.grml.org/       # share your knowledge
 http://grml.supersized.org/ # the grml development weblog
 #grml  <at>  irc.freenode.org    # meet us on irc
Hubert Gabler | 7 Mar 13:55 2007

Re: grml2hd: more files not found (was initrd.img not found)

Am Mittwoch, den 07.03.2007, 09:04 +0100 schrieb Michael Prokop:

> So to fix the issue just run:
> 
>   sed -i "s#/home/grml#/home/$USER#g" /home/$USER/.gkrellm2/user-config
>   sed -i "s#/home/grml#/home/$USER#g" /home/$USER/.gkrellm2/theme_config
>   sed -i "s#/home/grml#/home/$USER#g" /home/$USER/.idesktop/*.lnk
> 
Thank you! This workaround remarkably reduced the error messages!
I really dont want to strain your nerves too much, but one minor problem
remains:
after returning from the graphical desktop I read on the console:
Warning: Failed to open file(/usr/share/fluxbox/nls/de_AT/fluxbox.cat
and also
Keys: Invalid key/modifier on line 73; None XF86AudioMedia
Keys: Invalid key/modifier on line 74; None XF86AudioRaiseVolume
Keys: Invalid key/modifier on line 75; None XF86AudioLowerVolume
Keys: Invalid key/modifier on line 73; None XF86AudioMedia

Regards,
Hubert

Michael Prokop | 7 Mar 14:05 2007

Re: grml2hd: more files not found (was initrd.img not found)

* Hubert Gabler <loipersb <at> aon.at> [20070307 14:00]:
> Am Mittwoch, den 07.03.2007, 09:04 +0100 schrieb Michael Prokop:

[...]

> I really dont want to strain your nerves too much, but one minor problem
> remains:
> after returning from the graphical desktop I read on the console:
> Warning: Failed to open file(/usr/share/fluxbox/nls/de_AT/fluxbox.cat

Well, fluxbox does not ship language files for de_AT locales, see
/usr/share/fluxbox/nls/ for a listing. If you don't need them don't
care about it, otherwise adjust your locales.

> and also
> Keys: Invalid key/modifier on line 73; None XF86AudioMedia
> Keys: Invalid key/modifier on line 74; None XF86AudioRaiseVolume
> Keys: Invalid key/modifier on line 75; None XF86AudioLowerVolume
> Keys: Invalid key/modifier on line 73; None XF86AudioMedia

Your system does not provide XF86* keys/keymappings. Either
configure them with for example xmodmap or just ignore the message
or either remove the coresponding lines in your ~/.fluxbox/keys.

regards,
-mika-
-- 
You like grml?  Help us!      http://grml.org/donations/
Already on the grml-user-map? http://www.frappr.com/grmlusers
The Grml Planet               http://planet.grml.org/
Grml Solutions                http://solutions.grml.org/
* Hubert Gabler <loipersb <at> aon.at> [20070307 14:00]:
> Am Mittwoch, den 07.03.2007, 09:04 +0100 schrieb Michael Prokop:

[...]

> I really dont want to strain your nerves too much, but one minor problem
> remains:
> after returning from the graphical desktop I read on the console:
> Warning: Failed to open file(/usr/share/fluxbox/nls/de_AT/fluxbox.cat

Well, fluxbox does not ship language files for de_AT locales, see
/usr/share/fluxbox/nls/ for a listing. If you don't need them don't
care about it, otherwise adjust your locales.

> and also
> Keys: Invalid key/modifier on line 73; None XF86AudioMedia
> Keys: Invalid key/modifier on line 74; None XF86AudioRaiseVolume
> Keys: Invalid key/modifier on line 75; None XF86AudioLowerVolume
> Keys: Invalid key/modifier on line 73; None XF86AudioMedia

Your system does not provide XF86* keys/keymappings. Either
configure them with for example xmodmap or just ignore the message
or either remove the coresponding lines in your ~/.fluxbox/keys.

regards,
-mika-
--

-- 
You like grml?  Help us!      http://grml.org/donations/
Already on the grml-user-map? http://www.frappr.com/grmlusers
The Grml Planet               http://planet.grml.org/
Grml Solutions                http://solutions.grml.org/
Hubert Gabler | 7 Mar 18:40 2007

Re: grml2hd: more files not found (was initrd.img not found)

Am Mittwoch, den 07.03.2007, 14:05 +0100 schrieb Michael Prokop:
> Well, fluxbox does not ship language files for de_AT locales, see
> /usr/share/fluxbox/nls/ for a listing. If you don't need them don't
> care about it, otherwise adjust your locales.
> 

> Your system does not provide XF86* keys/keymappings. Either
> configure them with for example xmodmap or just ignore the message
> or either remove the coresponding lines in your ~/.fluxbox/keys.
> 
That did it! Thank you mika for your advice (and your patience).
I think it's time for a donation again ....

Regards,
Hubert


Gmane