DSL 0.7.2 HD install no workie
Forum: HD Install
Topic: DSL 0.7.2 HD install no workie
started by: UnDude
Posted by UnDude on Aug. 07 2004,23:35
Greetings,I am unable to perform a normal DSL 0.7.2 HD install on one of my old PCs. Here's my hardware configuration:
Tyan Tomcat III motherboard
Cyrix P166 CPU (P1-compatible, although Win XP won't install on this PC because MickySoft claims it's a 486
)128 MB RAM
IDE Primary Master = CD-ROM drive, Primary Slave = Maxtor 7 GB HD
I used Partition Magic 8 boot floppies to set up my partitions as follows:
hdb1 = 305.9 MB, FAT16, Win 95 OSR2 w/NTLDR as boot manager
Sectors 63 to 626,534 (CHS 0-1-1 to 38-254-63)
This partition is used mainly for disaster recovery and to hold the boot manager
hdb5 = 5,263.5 MB, FAT32, Win 2k Pro
Sectors 626,598 to 11,406,149 (CHS 39-1-1 to 709-254-63)
This is my main work partition
hdb6 = 502.0 MB, FAT16, Win NT 3.51 Workstation
Sectors 11,406,213 to 12,434,309 (CHS 710-1-1 to 773-254-63)
hdb7 = 604.0 MB, Ext2, DSL-ready
Sectors 12,434,373 to 13,671,314 (CHS 774-1-1 to 850-254-63)
I have copied both the HD MBR and hdb1's boot sector to files for safekeeping. I'd like to put LILO on hdb7 and keep NTLDR as my boot manager - assuming I get that far.
The DSL 0.7.2 CD boots fine, although I must specify video mode 0 (80 x 25) "Local APIC #0 not detected" as well as mouse location (PS/2 port) and video resolution and color depth.
Once on the DSL desktop, in xterm, I type "sudo dsl-hdinstall" and specify hdb7 as the target partition. I get:
Warning: ignoring extra data in partition table 6 (3 times)
Warning: invalid flag 0x395e of partition table 6 will be corrected by w(rite)
Sorry system has not detected a linux partition.
Hmmm, maybe I just have a "Sorry system"?
Next, I type "sudo cfdisk" and get:
FATAL ERROR: Cannot read disk drive
Press any key to exit cfdisk
Finally, I type "sudo fdisk -l" and get:
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 39 313236 6 FAT16
/dev/hdb2 40 851 6522390 5 Extended
/dev/hdb5 * 40 710 5389776 b Win95 FAT32
/dev/hdb6 ? 106306 176659 565108754+ 66 Unknown
Emelfm sees all partitions thru hdb7 just fine, and can mount, read, and write any of them.
Any help with this would be greatly appreciated.
Posted by mpie on Aug. 08 2004,00:21
weird thought but try it as a standard linux partition as the install process makes it ext2 anyway............. post the result, also are your partritions using all your harddrive some systems require a small amount of free disk for host protected info....just suggestions?
Posted by UnDude on Aug. 08 2004,03:25
I did try leaving hdb7 as unallocated space before booting the DSL CD, thinking that I could maybe create and format the partition from within DSL, but still no go. Cfdisk still can't see the HD at all, and fdisk still shows goofy info for hdb6.
Posted by roberts on Aug. 08 2004,06:23
This has been discussed before. There is a known issue with 0.7.2. It is fixed in 0.7.3
Posted by UnDude on Aug. 08 2004,19:38
Okay. I'll download 0.7.3 and give that a whirl.
Posted by UnDude on Aug. 14 2004,03:28
Well, guess what? I downloaded, burned, and booted DSL 0.7.3 and I get the exact same results when trying to do a HD install. Grrrrr...After playing with DSL, I booted a DOS floppy with Norton Disk Editor and took a peek at all the HD's partition tables, but I didn't see anything unusual in there.
Any ideas, anyone?
Posted by roberts on Aug. 14 2004,06:15
First you say:| Quote |
| hdb7 = 604.0 MB, Ext2, DSL-ready Sectors 12,434,373 to 13,671,314 (CHS 774-1-1 to 850-254-63) |
Yet what you really have is:
| Quote |
| Finally, I type "sudo fdisk -l" and get: Device Boot Start End Blocks Id System /dev/hdb1 * 1 39 313236 6 FAT16 /dev/hdb2 40 851 6522390 5 Extended /dev/hdb5 * 40 710 5389776 b Win95 FAT32 /dev/hdb6 ? 106306 176659 565108754+ 66 Unknown |
Where is the type 83 "linux" partition that dsl-install is looking for?
Posted by UnDude on Aug. 14 2004,16:43
Where is hdb7?Both Partition Magic and Norton Disk Editor see it just fine, and show it as type 83.
In DSL, emelfm also sees it just fine -- I can mount, unmount, read, and write to it.
fdisk does *not* see it and returns goofy info for hdb6, as you have seen.
cfdisk refuses to see hdb at all.
Go figure.
Posted by ckam2 on Aug. 14 2004,17:10
getting a simillar problem as undude.
Posted by nucpc on Aug. 14 2004,21:37
UnDude, ckam2,Had exactly the same trouble. `fdisk' didn't like my `too far for it' extended disk at all
and refused to acknowledge them (crashing the install script). In the end, when I reduced
my number of partitions (so that the disk wasn't extended anymore) I could get it to work.
UnDude - you seem on top of your game so you might consider editing the
dsl-install script; commenting out the fdisk checking lines....if you're sure you've got the
partition and you can write to it (which it looks like you have and can do) then there
shouldn't be a problem. Nine lines to comment out from FDISK="$(fdisk -l /dev/$DISK...
The variable is never used anywhere else.
I however never tried this, I just reduced my number of partitions instead.
All the best.
Posted by Rapidweather on Aug. 15 2004,21:51
Don't know if this will help, but I use either tomsrtbt or BootE linux (on a floppy) to set up a hard drive and format the partitions for ext2, swap, etc.--
I have not been able using 0.6.2 or 0.6.3 (oldies) to do a "dsl-hdinstall" and
have it boot up fully to X. Some get up to run level 2 (text).
--
Something like Mandrake 7.2 will easily install, set up GRUB, and boot right up into KDE. It's similar to Redhat 6.1, but easier. Most of the time, my
dsl-hdinstall will set up a lilo that won't fully boot, or boots to a different point each time, without getting the linux system to run.
---
I don't know, maybe GRUB is better, or the install script Mandrake uses
is better, etc.
--
I'm using a IBM 350-P90, with an upgrade 200 MMX processor and 128 MB ram, on a 420 MB HDD. Works fine with an older kernel such as
in Mandrake 7.2. I run Opera 6.03, and have my own dialer setup as shown here:
< http://www.geocities.com/rapidweather/linux2.html >
--
I have found that some of the older kernels run better on old hardware, not suprisingly, and although they will run the newer DSL kernels, they use up all the RAM, and can have other problems, but will work.
--
All in all, I find that DSL works best as a live CD, since I have not been able to get it to install using dsl-hdinstall. I do run it from the HDD from a boot floppy and /knoppix folder in a partition. Also, the filetool.lst and backup.tar.gz are placed in another partition, and the boot is done thusly:
boot: knoppix restore=/dev/hda2
I have a couple of machines that run DSL like that, and one that uses the CDROM drive, but with a restore partition as per above.
I'm going to keep trying on the dsl-hdinstall, I have an older machine that I may be able to use, I'll have to see...
I still have doubts about the "vga=791" being passed by the lilo script, or
whatever. Once the DSL system is installed on the HDD, and at least boots up to a text level, I find that X can fail, and I cannot edit lilo.conf
using the live CD to get in to the system. When I run lilo, it uses the default lilo.conf, with the same unaltered result.
--
All in all, I am convinced that DSL can be installed to the HDD, if Mandrake 7.2 can. Perhaps I need to download the latest DSL and use the dsl-hdinstall scripts provided there.
---
Posted by UnDude on Aug. 18 2004,04:22
Hey, I finally got the DSL 0.7.3 HD install to work. Woohoo!Here's how it was done:
The first step was to boot my DOS Norton Disk Editor floppy and save the HD's mbr to a file on hdb1 for safekeeping.
After booting the DSL CD, I snooped through the directory structure until I found the dsl-hdinstall script in the /KNOPPIX/usr/sbin directory. I copied the script to the /root directory and renamed it to dsl-hdinst.
| Quote (nucpc @ Aug. 14 2004,17:37) |
| UnDude - you seem on top of your game so you might consider editing the dsl-install script; commenting out the fdisk checking lines....if you're sure you've got the partition and you can write to it (which it looks like you have and can do) then there shouldn't be a problem. Nine lines to comment out from FDISK="$(fdisk -l /dev/$DISK... The variable is never used anywhere else. |
Next, I followed nucpc's suggestion, editing dsl-hdinst to remove the if statement involving fdisk.
Running dsl-hdinst and specifying hdb7 as the target partition now appeared to run normally. I chose the "standard" installation and did not set up for multiple users.
mkliloboot installed lilo on hdb's mbr.
I then booted the HD. "KNOPPIX" was the only available choice in lilo, but DSL now booted from the HD, asking for root and dsl user passwords. Success at last! I liked the fact that DSL remembered my selected screen resolution (800 x 600, my eyes are already bad enough without straining them to read higher resolutions) and displayed a message about running xsetup.sh should I wish to change it.
Since I want lilo on hdb7's boot sector instead of hdb's mbr so that I can use ntldr as my boot manager, I returned to Norton Disk Editor, copied the mbr (lilo) to a file on hdb1 as well as to hdb7's boot sector. Then I overwrote the mbr with the original version, saved earlier.
Rebooting the HD now presented me with my original ntldr boot menu, so I booted hdb1 (Win95), then added the saved lilo boot sector file to ntldr's boot.ini, adding "Damn Small Linux" to my boot menu.
Booting the HD again and selecting DSL from the ntldr menu now booted me straight into hdb7 without a hitch.
As I was beginning to suspect, the problems I had trying to do a DSL HD install apparently involve the Linux fdisk and cfdisk commands. Editing fdisk out of the dsl-hdinstall script might also help ckam2 with his HD install.
This is cool. This is neat. Now I can play around with DSL on my hard drive. My current goal with DSL is to eventually customize it into a "kiosk" or "internet cafe" type of system with internet access and a few games, remaster it, then do a frugal install so that the user can't permanently change (read: screw up) any of the system settings. The user should also not have to know anything about Linux or hardware -- they just turn it on and it works.
I have a couple questions:
I have Mandrake 9 installed on two of my other PCs, and I seem to recall an option that allows you to install lilo on either the Linux partition's boot sector or a floppy disk instead of the HD's mbr. Is there such an option with DSL's lilo?
Also, when I boot DSL, I get the message, "You passed an undefined mode number. Press RETURN to see video modes available, SPACE to continue, or wait 30 seconds." Is there any way to bypass this automatically, as though you has pressed the space bar (I'm looking for faster bootup without any required user intervention here)?
Posted by cbagger01 on Aug. 18 2004,11:33
Add the option "vga=normal" to the Linux boot command append line inside your Lilo configuration file.Then run Lilo from the command line to rebuild your boot sector.
DSL will then boot up in "Normal" 80x25 text mode and you won't get that undefined mode number message/prompt any more.
Posted by ckam2 on Aug. 19 2004,01:09
yes, it worked.thanks
Posted by UnDude on Aug. 19 2004,22:02
Lilo wouldn't accept a "vga=" statement in lilo.conf's "append" line, but replacing the existing "vga=some_number" with "vga=normal" did the trick. Also, changing the "boot=" line from hdb to hdb7 put lilo where I wanted it, preserving my existing mbr.I even figgered out how to change my wallpaper by copying and modifying an existing desktop theme.
Now I can start playing around with this and maybe learn a little more about how DSL and Linux in general work.
The first order of business is to see if I can get DSL to recognize my remaining peripherals, like my ethernet and sound cards.
I would be curious, though, to know if there is a fix for the problems with fdisk and cfdisk that I (and probably quite a few others as well) encountered during DSL's HD installation process.
Again, thanks for all your help!
