Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
01-27-2023, 02:43 PM
|
#1
|
Member
Registered: Oct 2020
Posts: 399
Rep: 
|
Possibilities when old BIOS CHS & LBA HD addressing do not match?
BIOS recognizes HD but won't support it.
BIOS[pic] can id the HD (Primary Master), but sees two different capacities based on the addressing method:
CHS 8,446 MB
LBA 20,020 MB (actually capacity)
"Type:" is fixed as [Auto].
HD won't boot or recognize an os.
Booting by CD (Win 98 incidentally), I get a capacity approximately matching CHS. Perhaps because this older BIOS won't recognize a HD larger than 8 MB?
|
|
|
01-27-2023, 08:17 PM
|
#2
|
Member
Registered: May 2022
Location: New Mexico, USA
Distribution: Slackware 15.0 & 64 bit-current, antiX
Posts: 118
Rep:
|
hi JASlinux,
One thing to check is the jumper on the hard
drive to make sure it is in master or slave position.
Some drives had a jumper setting that would limit the usable size.
Also see if the hard drive lists the CHS numbers to manually put them in the bios.
Does Windows 98 fdisk see the 20GB or just the 8GB?
If you can boot Linux, you can see if cfdisk or gparted sees the size correctly.
You can force LBA addressing with Lilo, not sure on Grub boot loader.
On a machine that old, you will be real limited on what you can do with modern software too.
Last edited by linuxdaddy; 01-27-2023 at 08:30 PM.
Reason: Added to it.
|
|
|
01-27-2023, 08:33 PM
|
#3
|
Moderator
Registered: Aug 2002
Posts: 26,757
|
The size jumper was typically for larger drives to limit them to 32GB although there might of been a 2.1GB limit too.
The c: drive looks empty from the picture, was or is it supposed to be bootable? Were there DOS system files supposed to be on the disk? Did you format the drive but forget to copy the system files via the sys command? If you did I would have expected to see at least the command.com file. What do you mean by won't recognize an OS?
It could be a BIOS limitation but if so I would not have expected to see the LBA info. It has been a long time since I have played with a PC that old. What are the other settings besides auto?
|
|
|
01-27-2023, 09:33 PM
|
#4
|
Member
Registered: May 2022
Location: New Mexico, USA
Distribution: Slackware 15.0 & 64 bit-current, antiX
Posts: 118
Rep:
|
thx michaelk,
It's been forever since I messed with a bios or hdd that old for the size jumper. A quick search on that Seagate drive shows the
CHS should be 16383 cylinders, 16 heads, 63 sectors versus what is shown.
Last edited by linuxdaddy; 01-27-2023 at 09:42 PM.
Reason: typo and added to it
|
|
|
01-28-2023, 02:55 AM
|
#5
|
Member
Registered: Oct 2020
Posts: 399
Original Poster
Rep: 
|
Thoughtful insights.
linuxdaddy:
I usually have my jumpers in the cable select position. I would expect a slave drive jumper setting might not boot, but then would BIOS even recognize it as a primary master?
I didn't check fdisk. I have since removed the drive to see if I can boot Linux as with 20 GB HD installed it won't boot anything.
I have also the original 6 GB Win98 HD which might boot, though today's goal for that machine is scanning. The printer utility requires XP or later.
michaelk: What happened is the Windows install CD offered to reformat, the process began, & at 99% an error reported the drive was not formatable without reason.
It's possible I could have partitioned off the 1st 8GB, but I do not remember or know if that would make the difference.
I meant that the BIOS does not see an OS on the drive despite one being there (XP when it was installed on a different machine).
linuxdaddy:
(Printed HD specs)
16,383 Cyl
16 HDS
63 Sect
39,102,336 LBA
Obviously in original post I meant GB.
|
|
|
01-28-2023, 03:19 AM
|
#6
|
Member
Registered: Oct 2020
Posts: 399
Original Poster
Rep: 
|
New secondary dilemma:
The HD is nominally 20 GB.
BIOS reports a head & cylinder discrepancy but equal capacity (7.87 GB), the same reported by DOS.
I think I remember seeing the drive at full capacity which is a bit confusing. 
|
|
|
01-28-2023, 03:23 AM
|
#7
|
Member
Registered: Oct 2020
Posts: 399
Original Poster
Rep: 
|
Summarily I am just trying to boot XP, & on my alternatives list is a VirtualBox. If that can run the printer utility & connect to wi-fi on a 64-bit Linux machine, that would be a more elegant solution than fussing with clunky old hardware.
|
|
|
01-28-2023, 04:09 AM
|
#8
|
Moderator
Registered: Aug 2002
Posts: 26,757
|
VB was going to be my next suggestion.
What type of printer, Parallel or USB? The virtual network adapter is linked to the physical device so no xp wireless driver is required.
|
|
|
01-28-2023, 07:53 AM
|
#10
|
Member
Registered: Oct 2020
Posts: 399
Original Poster
Rep: 
|
Quote:
Originally Posted by michaelk
What type of printer, Parallel or USB? The virtual network adapter is linked to the physical device so no xp wireless driver is required.
|
It's a wireless that probably also connects USB. I refuse Win 10 updates so I can't connect to the Internet in it.
As XP doesn't force those updates & it's not needed for browsing, it would most efficiently do the job.
|
|
|
01-28-2023, 08:36 AM
|
#11
|
Moderator
Registered: Aug 2002
Posts: 26,757
|
XP does not force updates because it stopped being supported in 2009 (extended in 2014)...
If you still have the printer drivers for XP I would guess it will work over wireless.
|
|
|
01-28-2023, 08:15 PM
|
#12
|
Member
Registered: May 2022
Location: New Mexico, USA
Distribution: Slackware 15.0 & 64 bit-current, antiX
Posts: 118
Rep:
|
If you can find a Windows 7 driver and use VB would be good too. What printer? won't it work on Linux for scanning?
|
|
|
01-28-2023, 08:20 PM
|
#13
|
Member
Registered: May 2022
Location: New Mexico, USA
Distribution: Slackware 15.0 & 64 bit-current, antiX
Posts: 118
Rep:
|
On the earlier post with CHS calculator, the sector size will be higher
than 512, like 1024,2048, 4096 etc for most hard drives and file systems.
|
|
|
01-28-2023, 09:41 PM
|
#14
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,501
|
Quote:
Originally Posted by Debian6to11
|
In case you didn't notice, that manual shows the same CHS values for 20G, 40G, 60G & 80G drives. I have a 20G IBM Deskstar IC35L020AVVN07-0 here claiming 16383/16/63 on its label, and a 1T Hitachi HUA722010CLA331 here claiming 16383/16/63 on its label. 16383/16/63 is the official CHS size for all HDDs of more than ~8G that specify any CHS size. 16383/16/63 is not expected ever to match the LBA size on HDDs >~8G. 16383/16/63 is 8,455,200,768 bytes on a 512B/sector HDD. 16383/16/63 are fictions designed for use by ancient BIOS, and ignored by anything newer. SPT vary according to distance from center on HDDs made this century and for many years prior, called zone bit recording. Physical heads are usually 2 per platter, often only 1. Physical "cylinders" or "tracks" vary according to whatever the bit density on the platters produces.
I remember once upon a time with some BIOS that if values were ever selected for a particular drive, that the BIOS could not reconcile them to LBA size, and would not accept the drive to proceed with POST, until after a CMOS clear, and leaving all the HDD settings on AUTO. IOW, always leave set to AUTO, meaning CHS values untouched (blanks or zeros) for drives larger than ~8G.
|
|
|
01-29-2023, 04:38 AM
|
#15
|
Member
Registered: Jan 2022
Location: Limassol, Cyprus
Distribution: Debian
Posts: 382
Rep:
|
Indeed I went through the manual very quickly. And a slow read today did not reveal anything useful.
I made some calculations and maybe 63x16x38792 could be close to correct value. It does give the 39102336 guaranteed sectors described in the manual. I suggest OP tries this even though I could be wrong. As far as I remember 16x63 was like a standard, or at least i remember seeing that to a few disks
Edit. https://www.seagate.com/staticfiles/...g100129216.pdf
And according to this install guide, troubleshooting, 5, "Verify that your BIOS
has autodetect and LBA mode enabled". /Edit
Last edited by Debian6to11; 01-29-2023 at 04:43 AM.
|
|
|
All times are GMT -5. The time now is 08:54 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|