Similar Threads:
1.installing patch 112438-02
I need help to understand the error I have when I try to install this
patch on my solaris system.
the error I have is :
pkgadd: ERROR: PKG parameter <SUNWcarx> does not match instance
<sunwcarx.u>
Dryrun complete.
thanks
annamaria
2.Patch 112438 on Solaris 2.6
Hello all,
Is there a way that I can apply Sun's 112438 patch on a Solaris
2.6 system. The patch says that it is for Solaris 7-8, but in the
readme file, it states "For Solaris 2.0-2.6 releases, refer to the
Install.info file and/or the README within the patch for instructions
on using the generic 'installpatch' and 'backoutpatch' scripts
provided with each patch."
I haven't found any such information... yet.
Some advice please!
Thanks,
-Greg
3.LILO giving 01 01 01 01 error
Hi folks,
I know I'm not the first person to observe this, but
LILO is starting up with L 01 01 01 01... on my older
laptop after I put my 40 gig hard drive in it.
The drive had worked just fine in a newer laptop.
I really prefer the older machine.
I've tried everything it seems, but I still get
the same L 01 01 01 effect. I tried:
* setting LBA32 mode, with no effect
* setting the hard drive CHS geometry, with no effect
I did this:
disk = /dev/hda
bios = 0x80
* running MSDOS fdisk /mbr, which caused an "invalid partition table"
error
* reinstalling LILO, producing the 01 01 error again.
* upgrading the BIOS, to no effect.
Does anyone know what else can be done?
Might GRUB be a better choice than LILO?
Thanks.
4.lilo and L 01 01 01 01 on older pc with 30GB hard disk
I'm having trouble installing slackware 10.2 on an old IBM Pentium Pro
PC with a 30GB maxtor. The old bios only sees 8G, so the previous user
had installed maxtor's maxblast/EZ-Bios for use with windoze. EZ-bios
caused problems with lilo after a slack install (IIRC, something like
"keyboard translation table not found"), so I used the maxblast floppy
to remove the ez-bios. I then repartitioned (1 large linux, 1 smaller
swap) and reinstalled a bare minimum slack (lilo in mbr on /dev/hda),
but when I try to boot from /dev/hda1 (swap is on /dev/hda2) I get the
"L 01 01 01 01" error. After reading the lilo docs and many usenet
posts, I tried numerous lilo options (lba32, fix-table, ignore-table,
specifying the geometry, etc.). Unfortunately, I still can't get the PC
to boot from the hard drive. Using lilo's test option showed two volume
id listings, one with a partition offset of 63 and the other with 0. I
believe lilo always picked the offset of 63. I tried specifying the
geometry using each value, with no luck. I even tried booting with a
dos diskette and ran fdisk /mbr, but that didn't help either.
If I use the slackware linux rescue disk, the PC boots and runs fine.
This clue, probably contains the answer, but I'm just not sure what it
is telling me.
Any ideas on how to make this hardware combo work without using the boot
floppy is appreciated. Is the answer that I need to create a small
(less than 8GB, within the 1024 cylinder limit) /boot partition? If so,
I was under the impression that the version of lilo (22.5.9) in
slackware 10.2 gets around this bios limitation - but I could be wrong.
Thank you for your help,
Peter
5.pci 0000:01:00.0: BAR 0: can't allocate resource
6. Problem installing gcc freware on Solaris Intel 01/06
7. unable to install patch 121018-01
8. Sol10 01/06 x86 Install Grub Prolem