I now did the same for this VL7, changed in fstab sdb6 to hdd6 and the bootingstops again as above saying can't open device /dev/hdd6.

How to go about?

With vl7 slack13 ubuntu suse fedora etc the new device system is now sd vs hd in fact the hd system is no longer maintained in the kernel, its available to build but is deprecated. All you have to remember is what used to be hdx is now sdx. So in your case if you are using /dev/hdb6 to install it will now be /dev/sdb6 (just substitute sd for hd the rest is the same). If you use lilo as your bootloader make sure all hdx is converted to sdx in your liloconf file. I am not sure from your post if you use a seperate /home partition or not I would try a reinstall and remember what was hd is now sd........hope that helped some.

I now did the same for this VL7, changed in fstab sdb6 to hdd6 and the bootingstops again as above saying can't open device /dev/hdd6.

How to go about?

With vl7 slack13 ubuntu suse fedora etc the new device system is now sd vs hd in fact the hd system is no longer maintained in the kernel, its available to build but is deprecated. All you have to remember is what used to be hdx is now sdx. So in your case if you are using /dev/hdb6 to install it will now be /dev/sdb6 (just substitute sd for hd the rest is the same). If you use lilo as your bootloader make sure all hdx is converted to sdx in your liloconf file. I am not sure from your post if you use a seperate /home partition or not I would try a reinstall and remember what was hd is now sd........hope that helped some.

Cheers,Vec

Thanks! Got it working. Posting from within now. Needed 2 more install. The previous to this install lilo /boot/tamu could not read the slackware properly. Next install I excluded this directory. Will do it manually.Internet and sound working. First impression very good except lilo splash looks awful.

I'm guessing the included qt4 still needs to be built against the libpng14 package. I'm getting the same png errors mentioned in the alpha 1 thread. Went away when I installed my own qt4 which was built against libpng14.

Not sure why but my lilo spash went away. Could have been me so maybe wait until you hear again of the same problem from another testor before you consider it a real problem.

Starting vasm as a normal user, then selecting SUPER from the menu results in an error.

vasm -->XWMSET offers the normal stable of window managers plus 'd', what the heck is 'd'.

That's all for now. Next 5 days are work days for me, so I'll just keep reporting what little I can. Hope to have some packages for contribution come my days off.

Next I could not anymore get into my working VL box with the new lilo. There were no errors, it just sat on the splash screen. Had to boot from install CDof VL6-STD and get my old lilo back with hda and hdd. Which means I cannotboot again into VL7. Can hda and sda be reconciled?If I use the lilo.conf file of VL7 in my working box get error :Fatal: raid_setup: stat("/dev/sda")

One thing: I boot with a standard screen and at midpoint in the boot process, the screen changes to a size very small and hard to read. I guess it starts at 640x480 (on a 1280x1024 screen) and then the screen changes to 1280x1024, with the text whizzing by at 640x480, leaving half the screen blank. I don't like this at all and would like to know if I can change it.

That is a 'feature' of more recent kernels. They automatically enable the framebuffer at native resolution. While I always did that anyway with a 'vga=' command in my Grub menu.lst, I find the new method untidy, and would much prefer not to have it happen. I don't think it is changeable, unfortunately.

Yuck! My current screen is 1280x1024. I hate to think of what it'll look like when I install on another computer with a 1600x1200 screen.--GrannyGeek

With vl7 slack13 ubuntu suse fedora etc the new device system is now sd vs hd in fact the hd system is no longer maintained in the kernel, its available to build but is deprecated. All you have to remember is what used to be hdx is now sdx. So in your case if you are using /dev/hdb6 to install it will now be /dev/sdb6 (just substitute sd for hd the rest is the same). If you use lilo as your bootloader make sure all hdx is converted to sdx in your liloconf file. I am not sure from your post if you use a seperate /home partition or not I would try a reinstall and remember what was hd is now sd........hope that helped some.

It didn't work quite so neatly on my system. /dev/hda became /dev/sdb. /dev/hde (where my Linux partitions live) became /dev/sda. My former /dev/hdb became /dev/sdc. My DVD drive is now /dev/sdd.

For some reason, LILO can't boot my partitions except for /dev/sda11 (VL7 Alpha 2.1). I get a kernel panic at about midpoint in loading the older systems. I did make sure lilo.conf had the correct /dev/sdx designations for my partitions, but lilo.conf was already that way. I tried changing the older partitions to /dev/hdx but that didn't work at all.

I have LILO on a floppy disk, so I just use a different floppy if I want to run an older Linux installation. On my other computer I'll have to use the CD for an earlier Linux, as it has no floppy drive.--GrannyGeek

I made it! I have again amultiple boot lilo. One into my VL6 working box, the othersinto VL7 and Slackware-13.1 resepectively.

Installed kernel-2.6.33.4 into my VL6 box. Did lilo with hd setting.Changed in fstab hd to sd.Rebooted with VL7CD.Changed lilo.conf with hd settings to new one with sd settings I copied from VL7.Did lilo.Rebooted and there I am in my VL6 box all set to sd.I must admit during the run my heartbeat accelerated a bit.

Now one problem, NVIDIA does not load. I copied /usr/src from VL7 to my box. According to nvidia log the gcc should be 4.4 version.Any suggestions?

QuoteThe compiler used to compile the kernel (gcc 4.4) does not exactly match the current compiler (gcc 4.2). The Linux 2.6 kernel module loader rejects kern el modules built with a version of gcc that does not exactly match that of t he compiler used to build the running kernel.

If you know what you are doing and want to ignore the gcc version check, sel ect "No" to continue installation. Otherwise, select "Yes" to abort install ation, set the CC environment variable to the name of the compiler used to c ompile your kernel, and restart installation.

Option "AllowEmptyInput" "false"Option "AutoAddDevices" "false"That fixes the problem.... but it's annoying when it acts crazy out of the box.. maybe something the devs could consider as a default fix.

Option "AllowEmptyInput" "false"Option "AutoAddDevices" "false"That fixes the problem.... but it's annoying when it acts crazy out of the box.. maybe something the devs could consider as a default fix.

Just checked it in firefox and there is no such problem. Keyboard keys working propely.