Legacy OS 2017 Released
Hi belham2 -
happy to be reporting success with my P4 laptop setup - I didn't mention, but I actually also tried ttuuxx's 214X-top11 on this machine to see if it might have rt61 wifi driver issues worked out. In my case, I used a Yumi usb install and copped the same rejection as you - "cannot find Puppy on 'atahd'..." And that is the main clue I reckon - my guess is that the initrd.gz whatyoumacallit doesn't allow for non-cd / non-hdd bootups. I was going to experiment with a marker file in the directory like I've seen in other setups (dummy files named "IDEHD" - is there a USBHD? can't recall offhand). But, since the other puppy6 distros on the usb were booting without marker files I didn't follow through. I was trawling through the 367-odd pages on the 214-topX thread for any evidence of usb-boot installs, but maybe if you contact ttuuxx directly he might help out, or someone might know how to modify the initrd.gz appropriately.
Good luck - I'm watching to see how you go
happy to be reporting success with my P4 laptop setup - I didn't mention, but I actually also tried ttuuxx's 214X-top11 on this machine to see if it might have rt61 wifi driver issues worked out. In my case, I used a Yumi usb install and copped the same rejection as you - "cannot find Puppy on 'atahd'..." And that is the main clue I reckon - my guess is that the initrd.gz whatyoumacallit doesn't allow for non-cd / non-hdd bootups. I was going to experiment with a marker file in the directory like I've seen in other setups (dummy files named "IDEHD" - is there a USBHD? can't recall offhand). But, since the other puppy6 distros on the usb were booting without marker files I didn't follow through. I was trawling through the 367-odd pages on the 214-topX thread for any evidence of usb-boot installs, but maybe if you contact ttuuxx directly he might help out, or someone might know how to modify the initrd.gz appropriately.
Good luck - I'm watching to see how you go
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
@belham2, I tried the following but it didn't work.
It keeps looking at hda1 for the main files. When I had the main files on sda1 it still couldn't find them. I tried sdb1 as it's an ext3 file system rather than a ext4.
I used my own uuid sourced from "blkid" in a terminal. I noticed you used the same one as Puppyt which would not be correct as uuid are unique.
I'm pretty sure when I looked in the initrd there was no pmedia=atahd.
Yep I was right. The following only seem to be supported:
Boot param PMEDIA= usbflash|usbhd|usbcd|ideflash|idehd|idecd|idezip|satahd|scsihd|scsicd
Ext3 seems Ok but there is no mention of Ext4.
I'm now going to try PMEDIA=idehd and satahd. I'm not confident.
Code: Select all
title Legacy OS 2017 (sdb1 ext3)
uuid 70fd6f6a-7df1-4cdf-a0ef-d04c5e55adca
kernel /vmlinuz root=/dev/ram0 pmedia=atahd pfix=fsck pfix=e2fsck
initrd /initrd.gz
I used my own uuid sourced from "blkid" in a terminal. I noticed you used the same one as Puppyt which would not be correct as uuid are unique.
I'm pretty sure when I looked in the initrd there was no pmedia=atahd.
Yep I was right. The following only seem to be supported:
Boot param PMEDIA= usbflash|usbhd|usbcd|ideflash|idehd|idecd|idezip|satahd|scsihd|scsicd
Ext3 seems Ok but there is no mention of Ext4.
I'm now going to try PMEDIA=idehd and satahd. I'm not confident.
Neither idehd or satahd worked.
It seemed to be looking at the correct drive which is hda2,0. My boot drive is sdc1 which according to grub4dos is hd0,0 therefore sda1 is hd1,0 and sdb1 is hd2,0.
It appears to be trying to boot in pupmode=1
I guess it can't read my drives, maybe they are too new.
I'm out of ideas.
It seemed to be looking at the correct drive which is hda2,0. My boot drive is sdc1 which according to grub4dos is hd0,0 therefore sda1 is hd1,0 and sdb1 is hd2,0.
It appears to be trying to boot in pupmode=1
I guess it can't read my drives, maybe they are too new.
I'm out of ideas.
Ok so I've had *some* success with getting the d-link Air-PlusG DWL-G630 card with the rt61 chip up and running in Legacy2017. I've magpied pets and drivers from the 2007-2008 era of the Murga forums, and some commandline tips too. I'll post some example links below of where I journeyed, but it is a bit of hit and miss. For John - three things I've noticed in my travails 1)no devx available, for compiling ormaking pets etc that are otherwise unavailable - such as https://help.ubuntu.com/community/WifiD ... RalinkRT61. Would ttuuxx's devx for 214X work in this regard? 2)The wifi network manager here http://www.murga-linux.com/puppy/viewtopic.php?t=21177 (revised Network Wizard + dhcpcd Aug 24 2007) works really well in Legacy2017, has the WPA2 button, looks good without the additional selection options that are a bit confusing for me (i.e.,"WPA Driver" (Atheros/Prism/other) and "AP Scan" options (Supplic/Driver/Hidden), and 3) doesn't seem to have a "remove pet" option, like I guess I'm used to in Puppy over the last couple of years. Perhaps there's a commandline way to check that the pets that might be added to Legacy2017 are working appropriately without missing dependencies or some sort of conflicts?
I actually got connected to the wifi network out of Legacy2017 using the DWL-G630! Woo-hoo! Screeny attached...
I actually got connected to the wifi network out of Legacy2017 using the DWL-G630! Woo-hoo! Screeny attached...
- Attachments
-
- snapshot8.png
- (101.7 KiB) Downloaded 485 times
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
hey smokey01 sorry for your setback. I have the older style IDE PATA in this machine, though I don't know if that makes a difference. What I did was to partition an ext2 section of my hdd and immediately install Legacy2017 frugally on it, without altering the default settings offered by its Grub2. I installed grub2 to MBR. When I rebooted, I observed 2 screen lightening/darkenings as grub tried to boot my Legacy selection, before it defaulted and booted WinXP. So I had a puppy431 on cd to hand, and used it live to test the hardware and over-write the grub2 install on the MBR, as provided above. It automated the uuid, and fingers crossed it rebooted and has been working great ever since. Apart from the wifi...
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
...and before I interrupted to commiserate with smokey01, I have to say that my wifi woohoo was short-lived. I was flicking through some connection choices and chose 'automatic' connection rather than "load Telstra65.." and it used one of the non-encrypted, open / hotspot connections of "Telstra Air" or "Fon Wifi". It connected, but subsequently failed and has done so unsuccessfully using network wizrd (sic), wlassist or RutilT. So I thought maybe the encryption handshakey-thingy of the connectivity was the drama, but now with rebooting a few times to the same pattern of non-connectivity I'm not so sure. More shortly with links to the resources I used (dinner's on!)
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
Right so the resources I used were (in no particular order):
Extra drivers for Puppy 2 with 2.6.18.1 kernel http://www.murga-linux.com/puppy/viewtopic.php?t=43653, with this message interesting http://www.murga-linux.com/puppy/viewto ... 134#597134;
Ralink RT61 PCMCIA wifi transfer speed capped at 130k? http://www.murga-linux.com/puppy/viewtopic.php?t=30258;
How to connect RT61 wireless with WPA? http://www.murga-linux.com/puppy/viewtopic.php?t=20966;
WPA with RaLink RT61 wireless chip (SOLVED) http://www.murga-linux.com/puppy/viewtopic.php?t=17522;
Getting WPA working under Network Manager and RT73 [solved] http://www.murga-linux.com/puppy/viewtopic.php?t=18535;
revised Network Wizard + dhcpcd Aug 24 2007 http://www.murga-linux.com/puppy/viewtopic.php?t=21177;
How to configure wifi from the commandline http://www.murga-linux.com/puppy/viewtopic.php?t=22469; and,
ndiswrapper in puppy after version 2.14 http://www.murga-linux.com/puppy/viewtopic.php?t=25895
And now I'm a little concerned with the number of RT61 modules/yenta sockets I seem to have collected since my last dmesg:
Anyone welcome to jump in with suggestions regarding a suitable strategy to get the DWL-G630 (RT61) working in Legacy2017, cheers
Extra drivers for Puppy 2 with 2.6.18.1 kernel http://www.murga-linux.com/puppy/viewtopic.php?t=43653, with this message interesting http://www.murga-linux.com/puppy/viewto ... 134#597134;
Ralink RT61 PCMCIA wifi transfer speed capped at 130k? http://www.murga-linux.com/puppy/viewtopic.php?t=30258;
How to connect RT61 wireless with WPA? http://www.murga-linux.com/puppy/viewtopic.php?t=20966;
WPA with RaLink RT61 wireless chip (SOLVED) http://www.murga-linux.com/puppy/viewtopic.php?t=17522;
Getting WPA working under Network Manager and RT73 [solved] http://www.murga-linux.com/puppy/viewtopic.php?t=18535;
revised Network Wizard + dhcpcd Aug 24 2007 http://www.murga-linux.com/puppy/viewtopic.php?t=21177;
How to configure wifi from the commandline http://www.murga-linux.com/puppy/viewtopic.php?t=22469; and,
ndiswrapper in puppy after version 2.14 http://www.murga-linux.com/puppy/viewtopic.php?t=25895
And now I'm a little concerned with the number of RT61 modules/yenta sockets I seem to have collected since my last dmesg:
Code: Select all
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 11, io base 0x0000bf40
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: irq 11, io base 0x0000bf20
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 11, io mem 0xf6f7fc00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 6 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
hda: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Registering unionfs 20060916-2203
unionfs: debugging is not enabled
fuse init (API version 7.7)
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
Adding 3168248k swap on /dev/hdc3. Priority:-1 extents:1 across:3168248k
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 845G Chipset.
agpgart: Detected 8060K stolen memory.
agpgart: AGP aperture is 128M @ 0xe0000000
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 7 (level, low) -> IRQ 7
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 59309 usecs
intel8x0: clocking to 48000
linmodem(1226): linmodem v0.1 loaded
pctel_hw: module license 'GPL linked with proprietary libraries' taints kernel.
pctel_hw(151): PCTel hardware driver version 0.9.7-9-rht-6 for PCT789
pctel(670): pctel v0.1 loaded
pctel_pci(526): pciserial_init_one: invalid pctel_hw binary module
pctel_hw: probe of 0000:00:1f.6 failed with error -22
b44.c:v1.01 (Jun 16, 2006)
ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNKB] -> GSI 7 (level, low) -> IRQ 7
eth0: Broadcom 4400 10/100BaseT Ethernet 00:0d:56:a8:28:a1
Yenta: CardBus bridge found at 0000:02:04.0 [1028:0149]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:04.0, mfunc 0x00001002, devctl 0x64
Yenta: ISA IRQ mask 0x0478, PCI irq 11
Socket status: 30000020
Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06
pcmcia: parent PCI bridge I/O window: 0xd000 - 0xefff
cs: IO port probe 0xd000-0xefff: clean.
pcmcia: parent PCI bridge Memory window: 0xf8000000 - 0xfdffffff
pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x89ffffff
pcmcia: Detected deprecated PCMCIA ioctl usage from process: cardmgr.
pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x800-0x8ff: excluding 0x8e0-0x8e7
cs: IO port probe 0x100-0x4ff: clean.
cs: IO port probe 0xa00-0xaff: clean.
pccard: CardBus card inserted into slot 0
lp: driver loaded but no devices found
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
rt61 1.1.0 BETA1 2006/06/18 http://rt2x00.serialmonkey.com
RT61: Vendor = 0x1814, Product = 0x0302
PCI: Setting latency timer of device 0000:03:00.0 to 64
01:23:45:67:89:00:00:00:00:00:00:00:00:00:00:00:
RT61: RfIcType= 3
01:23:45:67:89:00:00:00:00:00:00:00:00:00:00:00:
RT61: RfIcType= 3
ACPI: AC Adapter [AC] (on-line)
ACPI: Battery Slot [BAT0] (battery present)
01:23:45:67:89:00:00:00:00:00:00:00:00:00:00:00:
RT61: RfIcType= 3
ra0 (WE) : Driver using old /proc/net/wireless support, please fix driver !
01:23:45:67:89:00:00:00:00:00:00:00:00:00:00:00:
RT61: RfIcType= 3
01:23:45:67:89:00:00:00:00:00:00:00:00:00:00:00:
RT61: RfIcType= 3
01:23:45:67:89:00:00:00:00:00:00:00:00:00:00:00:
RT61: RfIcType= 3
01:23:45:67:89:00:00:00:00:00:00:00:00:00:00:00:
RT61: RfIcType= 3
01:23:45:67:89:00:00:00:00:00:00:00:00:00:00:00:
RT61: RfIcType= 3
01:23:45:67:89:00:00:00:00:00:00:00:00:00:00:00:
RT61: RfIcType= 3
usb 4-3: new high speed USB device using ehci_hcd and address 2
usb 4-3: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
Vendor: TOSHIBA Model: TOSHIBA USB DRV Rev: PMAP
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sda: 31326208 512-byte hdwr sectors (16039 MB)
sda: Write Protect is off
sda: Mode Sense: 23 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 31326208 512-byte hdwr sectors (16039 MB)
sda: Write Protect is off
sda: Mode Sense: 23 00 00 00
sda: assuming drive cache: write through
sda: sda1
sd 0:0:0:0: Attached scsi removable disk sda
usb-storage: device scan complete
usb 4-3: USB disconnect, address 2
usb 4-3: new high speed USB device using ehci_hcd and address 3
usb 4-3: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
Vendor: TOSHIBA Model: TOSHIBA USB DRV Rev: PMAP
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sda: 31326208 512-byte hdwr sectors (16039 MB)
sda: Write Protect is off
sda: Mode Sense: 23 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 31326208 512-byte hdwr sectors (16039 MB)
sda: Write Protect is off
sda: Mode Sense: 23 00 00 00
sda: assuming drive cache: write through
sda: sda1
sd 1:0:0:0: Attached scsi removable disk sda
usb-storage: device scan complete
usb 4-3: USB disconnect, address 3
01:23:45:67:89:00:00:00:00:00:00:00:00:00:00:00:
RT61: RfIcType= 3
01:23:45:67:89:00:00:00:00:00:00:00:00:00:00:00:
RT61: RfIcType= 3
usb 4-3: new high speed USB device using ehci_hcd and address 4
usb 4-3: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
Vendor: TOSHIBA Model: TOSHIBA USB DRV Rev: PMAP
Type: Direct-Access ANSI SCSI revision: 06
SCSI device sda: 31326208 512-byte hdwr sectors (16039 MB)
sda: Write Protect is off
sda: Mode Sense: 23 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 31326208 512-byte hdwr sectors (16039 MB)
sda: Write Protect is off
sda: Mode Sense: 23 00 00 00
sda: assuming drive cache: write through
sda: sda1
sd 2:0:0:0: Attached scsi removable disk sda
usb-storage: device scan complete
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
@Smokey, give me a little more credit than that....I did use my UUID as brought back by blkid in terminal. I may noob it sometimes but I'm not a complete noob! I tried a few things, even edited the init & changed a few things, but the bugger would not boot. Stinker of it is that the usb-connected hard drive I'm using is a PATA 133, but I'm not busting it out its enclosure just to run Classic Pup (or any other pup tht requires that). So, I'm out of ideas too.smokey01 wrote:. I noticed you used the same one as Puppyt which would not be correct as uuid are unique.
@PuppyT, what about if you nuke all your current network setups & files, and then re-set Telestra up again. Also, is that the Broadcom B4401 in there? Holy crap, I thought my stuff was old...... (j/k ya, my old P4 from ~'99 has an even older version). Wish I could help more with your problem, but when it comes to wireless, I think we all got demons in our machines. Why? Because each of my hardware setups in the house that does have wireless seems to have its own ideas whether it wants to connect & work, or not---depending on the day of the week it seems.
Cheers belham2 yairs, the kit is old - but that is the point isn't it? Good tip on nuking, will probably have to go that way next when I have the time. This particular wifi hardware *just* fell between the cracks as far as kernel support went (Linux/Puppy Series 2) - and you can't spend all your time stamping out compatibility fires that could be corrected with ever-so-slightly-different hardware, as John hinted at much earlier You have to draw the line somewhere...
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
Seeing that Legacy booted in QEMU I thought I would try and boot it directly from an ISO with G4D, nope, same problem, same errors.
I also tried ttuuxxx 214X-top10.iso, same problems.
I tried to boot Fatdog64-710 by the same method just to make sure this method worked. It worked no problems.
The stanza I used. The ISO was on sda1.Maybe it's time to give up.
Sorry John, I gave it my best shot.
I also tried ttuuxxx 214X-top10.iso, same problems.
I tried to boot Fatdog64-710 by the same method just to make sure this method worked. It worked no problems.
The stanza I used. The ISO was on sda1.
Code: Select all
title FD710 ISO
find --set-root /Fatdog64-710.iso
map /Fatdog64-710.iso (0xff) || map --mem /Fatdog64-710.iso (0xff)
map --hook
chainloader (0xff)
Sorry John, I gave it my best shot.
If any one needs help getting LegacyOS 2017 to boot from a full (as Smokey and I are struggling with, 'frugal' does not work) install on a USB, or SD card, or MicroSD all because their motherboard is too old to recognize usb and/or external booting, let me know and I'll post the tips/steps on how any motherboard in existence will boot from a USB/SDCard/MicroSD provided that the OS was fully (in Legacy and Classic pups and similar old pups, all other pups can be 'frugal') installed to that said device first. it's just a matter of using a tiny trick on a burned CD to fool the motherboard & bios (any of them). Then that CD can be removed at your leisure anytime during bootprocess and/or afterward or you can even leave it in.
-
- Posts: 503
- Joined: Mon 09 Sep 2013, 00:00
- Location: Florida, USA
- Contact:
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
Sounds like you've got a more recent computer, like I have. My computer is eight years old (late 2008) and, although I haven't tried the latest version of Legacy, John's last Legacy (OS 2.1) wouldn't boot on this machine, and nor would ttuuxxx's 214X Top 10. Both were based on Puppy 2.14, and I think this is the problem.smokey01 wrote:Seeing that Legacy booted in QEMU I thought I would try and boot it directly from an ISO with G4D, nope, same problem, same errors.
I also tried ttuuxxx 214X-top10.iso, same problems.
I tried to boot Fatdog64-710 by the same method just to make sure this method worked. It worked no problems.
The stanza I used. The ISO was on sda1.Maybe it's time to give up.Code: Select all
title FD710 ISO find --set-root /Fatdog64-710.iso map /Fatdog64-710.iso (0xff) || map --mem /Fatdog64-710.iso (0xff) map --hook chainloader (0xff)
Sorry John, I gave it my best shot.
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.
belham2, (or anyone) I could use those instructions as I'm trying to usb boot on my compac presario 2500 but bios don't support. The usb works after puppy legacy is running from cd rom but I can't even remaster the cd since the burner doesn't work when I tried it.belham2 wrote:If any one needs help getting LegacyOS 2017 to boot from a full (as Smokey and I are struggling with, 'frugal' does not work) install on a USB, or SD card, or MicroSD all because their motherboard is too old to recognize usb and/or external booting, let me know and I'll post the tips/steps on how any motherboard in existence will boot from a USB/SDCard/MicroSD provided that the OS was fully (in Legacy and Classic pups and similar old pups, all other pups can be 'frugal') installed to that said device first. it's just a matter of using a tiny trick on a burned CD to fool the motherboard & bios (any of them). Then that CD can be removed at your leisure anytime during bootprocess and/or afterward or you can even leave it in.
Hi Iggy50,iggy50 wrote:belham2, (or anyone) I could use those instructions as I'm trying to usb boot on my compac presario 2500 but bios don't support. The usb works after puppy legacy is running from cd rom but I can't even remaster the cd since the burner doesn't work when I tried it.belham2 wrote:If any one needs help getting LegacyOS 2017 to boot from a full (as Smokey and I are struggling with, 'frugal' does not work) install on a USB, or SD card, or MicroSD all because their motherboard is too old to recognize usb and/or external booting, let me know and I'll post the tips/steps on how any motherboard in existence will boot from a USB/SDCard/MicroSD provided that the OS was fully (in Legacy and Classic pups and similar old pups, all other pups can be 'frugal') installed to that said device first. it's just a matter of using a tiny trick on a burned CD to fool the motherboard & bios (any of them). Then that CD can be removed at your leisure anytime during bootprocess and/or afterward or you can even leave it in.
Hey, do you have access to any other bootable machine (or even that one with a different OS, pup and/or otherwise)?
We need to make a CD with something called "Plop Boot Manager 5.0".
Second, you'll need to fully install Legacy OS to that USB (I know it doesn't work right now, but it will with Plop).
You see, what we do is plug both Plop CD and fully-installed legacy OS USB in, start the ole Compaq, and you'll suddenly see a grub4dos-like boot screen asking if you want to boot "LegacyOS" from the attached USB. Plop makes Compaq think that the attached USB is really an attached IDE/Sata drive
Then, when LegacyOS boots up and completely to the desktop, take Plop out of the CD tray and now you have LegacyOS running off the USB and an empty CD tray to do whatever.
So, you can remaster (and then burn it to a CD), and then shut stuff back down. Put the newly burned CD in the tray, and your remastered LegacyOS should boot right up!
Here's the link to Plop Boot Manager 5.0:
https://www.plop.at/en/bootmanager/download.html
I've used Plop a lot in situations with old computers that refuse to recongize the USB upon initial boot, and want only a hard drive and/or CD booted disk.
Let me know how it goes and if you have any other questions.
belham2, thanks for the help. I should have read your previous posts to this thread as I just wasted my time trying to get both frugal/full install to dedicated partition (ext2) and boot with grub2 working but each one just immediately reboots back to grub menu. So it looks like only way is a full install to usb then use plop cd instead of grub2 menu-entry (not grub4dos or legacy grub).
Following is my grub2 menu-entries to 40_custom script file:
The other problem with legacy OS 2017 is that I can't get wlan0 to work (b43legacy driver). However, I was able to frugal (manual) install Wary 5.5 puppy and wlan0 worked great. When Legacy scans for available access-points, the scanning times out real fast (~1 second), instead of the ~30 seconds that Wary gave it. Legacy then reported no access-points. I was hoping I could copy the setup-scripts/driver from Wary into this install of Legacy... is that even possible?
I really would like to get Legacy working on my compac 2500 (P4/512 Mb ram). First partition is Lubuntu with grub2 booting but really slow. When I run Legacy on live CD, it runs really fast.
Following is my grub2 menu-entries to 40_custom script file:
Code: Select all
#!/bin/sh
exec tail -n +3 $0
#echo "Adding 40_custom menu entries." >&2
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'Wary Puppy (frugal) HD 0, partition 3' {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set 740fbe79-f67c-49a3-9b6f-e1f3b06e2cdc
echo 'Wary Puppy ...'
linux /wary/vmlinuz pmedia=atahd psubdir=wary
echo 'Loading initial ramdisk ...'
initrd /wary/initrd.gz
}
# Next entry (not working yet)
menuentry 'Legacy Puppy (frugal) HD 0, partition 4' {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set 26f09c1b-42e1-4f71-9dfa-3e1cc2c94702
echo 'Legacy Puppy ...'
linux /legacy/vmlinuz pmedia=atahd psubdir=legacy
echo 'Loading initial ramdisk ...'
initrd /legacy/initrd.gz
}
I really would like to get Legacy working on my compac 2500 (P4/512 Mb ram). First partition is Lubuntu with grub2 booting but really slow. When I run Legacy on live CD, it runs really fast.
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
Some good news. Linux Format, a monthly Linux magazine published in the UK, has included a copy of Legacy OS on this month's DVDs. This month's issue focuses mostly on lower resource distros, such as AntiX, Tiny Core, Linux Lite and Peppermint, made to run on older computers.
http://www.linuxformat.com/
http://www.linuxformat.com/
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
Yes it is - it's great to see Legacy getting more exposure as well. I think my machine's too recent to be able to run it but I'd be happy to give it a go if it were possible.
The magazine also raises the question of whether there's still a place for 32-bit distros now that seemingly the whole distro world's gone over to 64-bit. It doesn't seem that long ago (maybe 2010) that I was having to write "64-bit" on the disk when I burnt a 64-bit distro off to a CD or DVD as nearly all distros back then were 32-bit - now it's the other way round.
The magazine also raises the question of whether there's still a place for 32-bit distros now that seemingly the whole distro world's gone over to 64-bit. It doesn't seem that long ago (maybe 2010) that I was having to write "64-bit" on the disk when I burnt a 64-bit distro off to a CD or DVD as nearly all distros back then were 32-bit - now it's the other way round.
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.