 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I don't understand why linux would modify the frequency/timings of cpu
> and
> memory, and even if it did, why it would have to modify BIOS to do that.
> (What good would it do to modify BIOS anyways? It would have to re-boot in
> order for the changes to become effective. BIOS is not something which is
> constantly running in the background. It just sets up the hardware and
> starts
> the OS and that's it.)
I thought this to be so, too. I was astonished to see that people seem to
have had some problems with this.
And I was not sure if this is true or not, so I asked.
BTW:
I did try the Ubuntu Live CD and it did reset my computer's clock to either
daylight saving time or universal time - both -1:00, so I cannot be sure
which.
This is no real problem, though, merely a very minor annoyance. Still, this
should not be.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
TC wrote:
> I did try the Ubuntu Live CD and it did reset my computer's clock to either
> daylight saving time or universal time - both -1:00, so I cannot be sure
> which.
>
> This is no real problem, though, merely a very minor annoyance. Still, this
> should not be.
The Linux Way(tm) seems to be to set the system clock to UTC and compute
local time from that depending on your timezone configuration. (Which,
on a live CD, is probably not set right anyway.) The Windows Way(tm) is
to set the system clock to local time...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp schrieb:
> I don't understand why linux would modify the frequency/timings of cpu and
> memory, and even if it did, why it would have to modify BIOS to do that.
> (What good would it do to modify BIOS anyways? It would have to re-boot in
> order for the changes to become effective. BIOS is not something which is
> constantly running in the background. It just sets up the hardware and starts
> the OS and that's it.)
Well, /nowadays/ that's how it is. Used to be different in DOS times.
Then again, that's quite a long time ago...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Warp schrieb:
> > I don't understand why linux would modify the frequency/timings of cpu and
> > memory, and even if it did, why it would have to modify BIOS to do that.
> > (What good would it do to modify BIOS anyways? It would have to re-boot in
> > order for the changes to become effective. BIOS is not something which is
> > constantly running in the background. It just sets up the hardware and starts
> > the OS and that's it.)
> Well, /nowadays/ that's how it is. Used to be different in DOS times.
DOS could change the CPU/memory frequency by modifying BIOS and without
having to reboot?
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp schrieb:
>>> I don't understand why linux would modify the frequency/timings of cpu and
>>> memory, and even if it did, why it would have to modify BIOS to do that.
>>> (What good would it do to modify BIOS anyways? It would have to re-boot in
>>> order for the changes to become effective. BIOS is not something which is
>>> constantly running in the background. It just sets up the hardware and starts
>>> the OS and that's it.)
>
>> Well, /nowadays/ that's how it is. Used to be different in DOS times.
>
> DOS could change the CPU/memory frequency by modifying BIOS and without
> having to reboot?
No, but BIOS did more back then than just start the OS. For instance,
hard disk access or keyboard input would be handled by the BIOS.
Back then, the role of the BIOS was still closer to its name ("Basic
Input/Output System) than it is nowadays: It really did basic input and
output handling even while the OS was running, and was far from evolving
into a hardware configuration interface. (Remember how CPU and memory
frequency would be configured via hardware jumpers or DIP switches, port
I/O addresses would be jumpered on the /expansion card/ the ports were
on, etc?)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jim Henderson wrote:
> openSUSE 11.1 and 11.2 RC (which is in final testing now) should include
> ntfs-3g, so should be able to mount the NTFS partitions without a problem.
I have no problem using ntfs-3g and mounting NTFS drives RW from my OpenSuse
11 that I downloaded many months ago. I don't know it's on the live CD, but
it's definitely in the distro somewhere.
> With the live media, everything runs of the media - no need to perform an
> installation. The media is primarily to permit a user wanting to "test
> drive" Linux to see some of the features/functionality and to ensure
> system compatibility prior to installation.
Yeah, I learned that one the hard way. :-)
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> I don't understand why linux would modify the frequency/timings of cpu and
> memory, and even if it did, why it would have to modify BIOS to do that.
Actually, during boot-up, something along the lines of "installing new
microcode" or "installing new firmware" or something like that scrolls by.
That always worried me, but I figured it either got reversed at the next
reboot or it was too late to do anything about it, and it never caused any
trouble.
I am curious what that's all about, tho.
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka wrote:
> Back then, the role of the BIOS was still closer to its name ("Basic
> Input/Output System) than it is nowadays: It really did basic input and
> output handling even while the OS was running,
That pretty much went away when OSes started running in real mode. By the
time you got away from 16-bit code, nobody used the BIOS for basic I/O any more.
But you knew that.
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 30 Oct 2009 18:17:49 +0100, Darren New <dne### [at] sanrrcom> wrote:
>
> Actually, during boot-up, something along the lines of "installing new
> microcode" or "installing new firmware" or something like that scrolls
> by. That always worried me, but I figured it either got reversed at the
> next reboot or it was too late to do anything about it, and it never
> caused any trouble.
>
> I am curious what that's all about, tho.
http://kerneltrap.org/node/2678
Typically, microcode updates are loaded by the BIOS, but not everyone
updates their BIOS when new microcode is released for their CPU.
--
FE
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Fredrik Eriksson wrote:
> Typically, microcode updates are loaded by the BIOS, but not everyone
> updates their BIOS when new microcode is released for their CPU.
Thank you!
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
