Language Selection

English French German Italian Portuguese Spanish

Login

Please allow up to an hour or so to receive your initial password. If you don't receive an email from us within a comfortable amount of time, you may email and request a password at r at schestowitz dot com. Please be sure to include your registered username.

You may also wish to check your spam folders as your initial email may have been misidentified as spam. Please also note that yahoo.com will not accept mail from TuxMachines.org due to ISP regulation listing in Spamhaus.

Thanks!
Spaces are allowed; punctuation is not allowed except for periods, hyphens, and underscores.
A valid e-mail address. All e-mails from the system will be sent to this address. The e-mail address is not made public and will only be used if you wish to receive a new password or wish to receive certain news or notifications by e-mail.
Provide a password for the new account in both fields.
Type the characters you see in this picture. (verify using audio)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.

More in Tux Machines

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more