Re: toshiba satelli 1800-712

[Maurizio Bongini <maurizio.bongini@poste.it>]

Hi Thomas

i searched without results the bugzilla site ....
my problem seems to be common to other people with my computer and other of 
the
same brand...   

take a look to these links...

http://www.ussg.iu.edu/hypermail/linux/kernel/0502.1/0946.html
http://gentoo-wiki.com/HARDWARE_Gentoo_on_Toshiba_Satellite_3005-S403

then this one..
http://www.weizmann.ac.il/home/fesegre/Linux_on_a_Toshiba_Satellite_1800-712.html
it is reported also by toshiba official  site !  
http://linux.toshiba-dme.co.jp/linux/eng/pc/sat1800_memo.htm


two years ago i added myself to the toshiba linux forum but the problem was 
not
resolved, as you can see by above links....

are you in contact with some people  working in toshiba to obtain technical 
data about ? IMHO this may truly help ,saving a lot of debugging time...
if you cannot obtain any info ,then ...:            

i need to ask you some little questions about your requirements:
my laptop currently run  with a mandriva 2006 distribution:
it is the same if i compile an alternate kernel with the existing mandriva
 source,or you  absolutely need suse ?
my laptop has a parallel port and i have an old  desktop running mandrake 10.1
i have not a cross parallel cable...
i have to find  one it or build it from a normal parallel cutting wires and 
soldering it making a cross connection ( i already done the work in the past 
with a lan cable). 

Thanks

 Maurizio 

 

On Friday 09 June 2006 16:15, Thomas Renninger wrote:
> Does the laptop have a serial adapter?
> If not, I don't know how to debug that (There will be firescope to
> redirect kernel output over firewire, but that is future).
>
> If yes, connect the machine over a crossed serial cable with another
> one. On the remote machine watch the serial output with e.g.
> screen /dev/ttyS0 57600
> On the machine that gets debugged add the kernel option
> console=ttyS0,57600
> You should now see the kernel messages popping up on the remote screen
> session.
>
> Try to boot a SuSE debug kernel.
> If it does not boot you have to compile the kernel yourself:
>  - Install the kernel-source.rpm
>  - cd /usr/src/linux
>  - cp arch/i386/defconfig.default .config
>  - Edit .config and search for ACPI_DEBUG and set this line to:
>      ACPI_DEBUG=y
>  - make
>  - make install modules_install
>  - mkinitrd
>  - add a new boot entry for the kernel/initrd in /boot/grub/menu.lst
>  - reboot
>
> Now you can enable extended ACPI debugging (carefully, not too high):
> echo 0x1F >/proc/acpi/debug_level
>
> I wonder whether the machine hangs while processing some ACPI functions
> and which.
>
> Best you first search on http://bugzilla.kernel.org whether a similar
> bug exists and try to help there.
> If there is none, create a new one describing your problem, assign it to
> the ACPI component and take me into CC, please.
>
> Thanks,
>
>      Thomas
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 

_____________________________________________________________
Email with attachment's size more than 1 Mb will no more be received