FreeBSD 5.3-BETA4 Available
BrunoC writes "Once again, the FreeBSD Project presents yet another beta release of FreeBSD 5.3. FreeBSD 5.3 BETA 4 features major bugfixes for ATA, 4BSD is now the default scheduler and overall stability has greatly improved. BETA 5 should hit the streets next week and should be the last BETA and a Release Candidate is scheduled too. 5.3 should be around by October 3rd. ISO images are available for those who want to help the testing process." (Use a mirror.)
For a dead project, they sure release a lot of betas...
Long live BSD! =)
I notice that FreeBSD now has a scsi emulation layer for atapi devices. Very nice. Might be time to take another look at FreeBSD.
My other Slashdot ID is much lower.
Will the ACPI work for broken implementations? I am talking about Sony Vaio's or old Thinkpads.
??
How bizarre. They only just switched the default scheduler from 4BSD to ULE. Now they've swapped it back. Anyone know why?
I am TheRaven on Soylent News
I switched over to FreeBSD a while ago because Debian was so out of date. I fell in love with FreeBSD because it's so easy to maintain. And Ports are awesome! I can run a stable OS with the most up-to-date (stable) software. Before I had to run unstable Debian to get the latest PHP/Postgres to install, unless I compile it myself.
The above is not worth reading.
that's because no one cares about compatibility with your broken BIOS.
Chill and stop trying to police every last little setting on your computer.
Well, neither have you, and you have all those numbers in your name to prove how cool you are.
_O_
.|< The named which can be named is not the true named
From your entire bug report, it seems pretty obvious that something is rather wrong with the ata controller and/or bios on your hardware.
I happen to have had 3 of the same Maxtor drives as you have, and the last surviving one is currently primary master in my router. (hint, replace them, I have had 2 of them give up within short time of eachother, and the 3rd one seems to be getting close to giving up)
All 3 have always worked with FreeBSD, Linux and Windows, without any confusion with regards to its CHS settings.
I did however follow the rather strong suggestion that my BIOS gives me to run the bios auto detect and select 'normal' mode for a drive on which I am going to use a unix like system. This results in a user configured drive (for as far as the standard cmos settings go)
Oh, and I also followed the recomendations to have the disk as primary, and a cd drive as slave instead of having it as primary like you have.
That it is not recognized that way during sysinstall seems rather suspicious to me.
Maybe FreeBSD needs some patches for detectign this broken hardware configuration, just as it did get a patch for dealing with the rather broken bios of the asus p2b-ds that I happen to use (apic is broken, resulting in an interupt storm when doing things according to the official standard)
If you think this problem affects more then your very specific case, I suggest talking about it on the mailinglists for -current, and try to be helpfull in getting a workaround, ie, that means accepting that it is in fact a problem of your hardware.
All that said, your comment regarding fdisk seems to be correct, and it should accept the alternative geometry if those fit within the physical number of sectors that the drive has.
I switched over my 5.2.1 personal server to 5.3-Beta3. Mostly for the NDIS driver so I can get my atheros wireless card to work in turbo mode. It runs great. Their ath drivers are much more mature than linux's madwifi they still can't do turbo, all though the man file said otherwise. I'm guessing it's an issue with my card(DWL-G520). I now have my 2 linux computers and this one using windows drivers using ndis wrappers. My wireless speeds are now up to acceptable.
I suppose I'll give this one ago, although by the time I get around to it, I'll probably be cvs up'ing beta5.
Understanding is a three-edged sword. -- Kosh Naranek
Enabling power management in the kernel would help. You are most likely comparingn linux w/power management vs FreeBSD w/o
Actually, this seems like a real problem as on at least two workstations I've had fdisk insisting the drive geometry was wrong. Specifiying the correct vallues to fdisk didn't help as it insisted with the old values.. But ultimately I could install the OS just fine even with the geometry set wrongly and it reports the partition sizes well.