
Ubuntu on Toshiba: Pitfalls
Technical part under the cut.
The desire to put Ubuntu on your typewriter arose a month after buying the laptop. The black and gray Toshiba A200 13O was bought so to speak for love, not for convenience. It all started with the murder of Vista on board, which was eliminated for some subjective reasons and due to software brightness adjustment. A bios was installed from the website of the producer under the pig (under Vista there is a bios on the site, under Khryusha-own). Appeared hardware brightness control, etc. But after not very comfortable, but pleasant-looking prettiness near Vista, it was rather dull to work on Piggy. Still, the desire to go forward. And I also wanted to not take a steam bath with the virus - come to the office with a laptop with linukha and not think that during maintenance you can infect a bunch of Windows machines with projects, which in monetary terms will bring a big loss to the office.
The first time I crammed into a typewriter 7.10. I played around, but could not configure so that when the ears are connected, the built-in speakers are cut down. I waited 8.04 - the problem did not go away, but I did not want to retreat. Not immediately, but by assembling Alsa with a specialist for Intel HDA, profanity, the options snd-hda-intel model = lenovo line in /etc/modprobe.d/alsa-base, I managed to get them to function normally. And then after rebooting you need to re-plug the plug.
Soon it turned out that for the operation of the bluetooth it was necessary to download Windows so that it would pick up the device, and then reboot into ubuntu, which, of course, was absolutely worthless. I started to dig. It turned out that you need to cut it manually with the command sudo toshset-bluetooth on. But then it all started. An error got out that the kernel supposedly does not hold my Toshiba: required kernel toshiba support not enabled . This is the Ubuntu, which I toshset comes by default ... If you try to load the module toshiba_acpi betrayed the no such device .
This can now be systematized in a couple of sentences and indicate that the bluetooth is not working due to problems with ACPI. But to come to such a conclusion, it took a lot of time ..
Then I remembered how one evening after several sleep modes my tobosha under ubunta almost burned up, because the fan simply didn’t cut in (!) . This is where the problems with ACPI fit into the course of events. For the same toshsetallows you to work with a fan. Naturally, fnfxd could not be discussed without loading the toshiba_acpi module .
The question arose - why is the module not loading? It begs that the system does not see Toshiba in the laptop. After some deliberation and noises, no idea was born.
BIOS
We need a native BIOS ... that went to the base from the factory. By the way, I recently discovered that on the Ubuntu website it is now indicated that the Toshiba A200 is compatible (?) With 7.10 and 8.04.
Those bios may well be involved in the commotion ... I downloaded the bios under whist. Well, let’s omit that they have a Windows path for Windows on the C drive (I have it on E) in the BIOS autoinstaller, they overcame it by manipulation. Duck also turned out to be a phoenix too, albeit turned into a whist ... And then I killed my native kada, put the pigs.
Here are such things. And I like Ubunt so much)) Although I sometimes manage to hang it at zero.
PS: get a backup of the factory BIOS toshiba a200 13o =)
upd0:
did similarly krig krig'u:
upd1:
during the discussion we found out that the native bios does not solve the problem
upd2:
apparently, the problem is that toshset does not work with toshibs on phoenix BIOSes
put omnibook:
sudo apt-get install subversion build-essential linux- source linux-headers-generic
svn co omnibook.svn.sourceforge.net/svnroot/omnibook/omnibook/trunk
cd trunk
make && sudo make install
sudo make load
add omnibook to / etc / modules
gedit /etc/modprobe.d/omnibook
there we shove options omnibook ectype = 12 userset = 1
now bluetooth works
for me bios under XP
There was a problem with sleep modes - after resuming operation, the cooling fan of the processor is not cut, bluetooth dies, etc.
The desire to put Ubuntu on your typewriter arose a month after buying the laptop. The black and gray Toshiba A200 13O was bought so to speak for love, not for convenience. It all started with the murder of Vista on board, which was eliminated for some subjective reasons and due to software brightness adjustment. A bios was installed from the website of the producer under the pig (under Vista there is a bios on the site, under Khryusha-own). Appeared hardware brightness control, etc. But after not very comfortable, but pleasant-looking prettiness near Vista, it was rather dull to work on Piggy. Still, the desire to go forward. And I also wanted to not take a steam bath with the virus - come to the office with a laptop with linukha and not think that during maintenance you can infect a bunch of Windows machines with projects, which in monetary terms will bring a big loss to the office.
The first time I crammed into a typewriter 7.10. I played around, but could not configure so that when the ears are connected, the built-in speakers are cut down. I waited 8.04 - the problem did not go away, but I did not want to retreat. Not immediately, but by assembling Alsa with a specialist for Intel HDA, profanity, the options snd-hda-intel model = lenovo line in /etc/modprobe.d/alsa-base, I managed to get them to function normally. And then after rebooting you need to re-plug the plug.
Soon it turned out that for the operation of the bluetooth it was necessary to download Windows so that it would pick up the device, and then reboot into ubuntu, which, of course, was absolutely worthless. I started to dig. It turned out that you need to cut it manually with the command sudo toshset-bluetooth on. But then it all started. An error got out that the kernel supposedly does not hold my Toshiba: required kernel toshiba support not enabled . This is the Ubuntu, which I toshset comes by default ... If you try to load the module toshiba_acpi betrayed the no such device .
This can now be systematized in a couple of sentences and indicate that the bluetooth is not working due to problems with ACPI. But to come to such a conclusion, it took a lot of time ..
Then I remembered how one evening after several sleep modes my tobosha under ubunta almost burned up, because the fan simply didn’t cut in (!) . This is where the problems with ACPI fit into the course of events. For the same toshsetallows you to work with a fan. Naturally, fnfxd could not be discussed without loading the toshiba_acpi module .
The question arose - why is the module not loading? It begs that the system does not see Toshiba in the laptop. After some deliberation and noises, no idea was born.
BIOS
Those bios may well be involved in the commotion ... I downloaded the bios under whist. Well, let’s omit that they have a Windows path for Windows on the C drive (I have it on E) in the BIOS autoinstaller, they overcame it by manipulation. Duck also turned out to be a phoenix too, albeit turned into a whist ... And then I killed my native kada, put the pigs.
Here are such things. And I like Ubunt so much)) Although I sometimes manage to hang it at zero.
upd0:
sudo toshset -bluetooth on
required kernel toshiba support not enabled.
sudo modprobe toshiba_acpi
FATAL: Error inserting toshiba_acpi (/lib/modules/2.6.24-16-generic/kernel/drivers/acpi/toshiba_acpi.ko): No such device
did similarly krig krig'u:
dmesg
...
sudo modprobe toshiba
...
dmesg
... not a supported Toshiba laptop
lshw
...
description: Notebook
product: Satellite A200
vendor: TOSHIBA
version: PSAE0E-00Y019RU
...
upd1:
during the discussion we found out that the native bios does not solve the problem
upd2:
apparently, the problem is that toshset does not work with toshibs on phoenix BIOSes
put omnibook:
sudo apt-get install subversion build-essential linux- source linux-headers-generic
svn co omnibook.svn.sourceforge.net/svnroot/omnibook/omnibook/trunk
cd trunk
make && sudo make install
sudo make load
add omnibook to / etc / modules
gedit /etc/modprobe.d/omnibook
there we shove options omnibook ectype = 12 userset = 1
now bluetooth works
for me bios under XP
There was a problem with sleep modes - after resuming operation, the cooling fan of the processor is not cut, bluetooth dies, etc.