This is also under 2.4.x possible (2.4.20-ev6 in my case): modprobe srm_env cd /proc/srm_environment/named_variables ls auto_action boot_osflags booted_dev char_set language boot_dev boot_reset booted_file dump_dev license boot_file bootdef_dev booted_osflags enable_audit tty_dev
Ionut On Thu, May 15, 2003 at 09:51:54AM +0200, David Duminy wrote: > Can you still access to your old kernel ? > If you can , you have to boot in 2.2.20 and use the /dev/srm device to set > the srm environment variables. > > David > > --On jeudi 15 mai 2003 09:22 +0200 Jens Kruse <[EMAIL PROTECTED]> wrote: > > >Hi, > > > >I successfully installed Debian 3.0 on my Alphaserver 1000A 5/333. > >Booting/Rebooting with aboot and Kernel 2.2.x works fine. > > > >After i installed kernel-2.4.18-generic I have the problem that the > >machine - shuts down to SRM and then > >- tries to boot again with flag 0 > >- normal SRM-commands (i.e. set, boot) don't work anymore > > > >To boot automatically I set 'boot_osflags 0' and 'auto_action boot'. > > > >Even a 'boot <cdrom-device>' doesn't work anymore, because it calls the > >flag 0 automatically > > > >My questions: > >- What would help to get a 'clean' shutdown/reboot? > >- Is it possible to cancel the aboot-sequence at startup to set > >'boot_osflags <empty>' (is a 'set boot_osflags' enough?)? > > > >Thanks in advance, > > > >Jens > > > > > >-- > >To UNSUBSCRIBE, email to [EMAIL PROTECTED] > >with a subject of "unsubscribe". Trouble? Contact > >[EMAIL PROTECTED] > > > > > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > -- *************** * Ionut Georgescu * http://www.physik.tu-cottbus.de/~george/ * Registered Linux User #244479 * * "In Windows you can do everything Microsoft wants you to do; in Unix you * can do anything the computer is able to do."
