bios bug error w/ feisty fawn on toshiba satellite a135 s4527

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in recently. We were wondering if this is still an issue for you? Thanks in advance.

Same laptop, same story
I can't get the number b/c it flashes by so fast

Have you tried using Gutsy or the Hardy Alpha 2 Live CD, available at http://www.ubuntu.com/testing , to see if it is still an issue with them? If it is could you please add the full contents of 'dmesg' as an attachment after a fresh boot? Thanks in advance.

iv'e had the problem since fiesty
 hope this helps!

[ 0.000000] Linux version 2.6.22-14-generic (buildd@palmer) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14 23:05:12 GMT 2007 (Ubuntu 2.6.22-14.46-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000003f680000 (usable)
[ 0.000000] BIOS-e820: 000000003f680000 - 000000003f700000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000003f700000 - 0000000040000000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
[ 0.000000] BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
[ 0.000000] 118MB HIGHMEM available.
[ 0.000000] 896MB LOWMEM available.
[ 0.000000] found SMP MP-table at 000f7670
[ 0.000000] Entering add_active_range(0, 0, 259712) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 229376
[ 0.000000] HighMem 229376 -> 259712
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 259712
[ 0.000000] On node 0 totalpages: 259712
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 1760 pages used for memmap
[ 0.000000] Normal zone: 223520 pages, LIFO batch:31
[ 0.000000] HighMem zone: 237 pages used for memmap
[ 0.000000] HighMem zone: 30099 pages, LIFO batch:7
[ 0.000000] DMI present.
[ 0.000000] ACPI: RSDP signature @ 0xC00F75E0 checksum 0
[ 0.000000] ACPI: RSDP 000F75E0, 0014 (r0 TOSCPL)
[ 0.000000] ACPI: RSDT 3F6888C2, 0054 (r1 TOSCPL TOSCPL00 6040000 LTP 0)
[ 0.000000] ACPI: FACP 3F690C78, 0074 (r1 TOSCPL CALISTGA 6040000 LOHR 5A)
[ 0.000000] ACPI: DSDT 3F68A62D, 664B (r1 TOSCPL CALISTGA 6040000 INTL 20060608)
[ 0.000000] ACPI: FACS 3F691FC0, 0040
[ 0.000000] ACPI: SLIC 3F690CEC, 0176 (r1 TOSCPL TOSCPL00 6040000 LOHR 0)
[ 0.000000] ACPI: APIC 3F690E62, 0068 (r1 INTEL CALISTGA 6040000 LOHR 5A)
[ 0.000000] ACPI: HPET 3F690ECA, 0038 (r1 INTEL CALISTGA 6040000 LOHR 5A)
[ 0.000000] ACPI: MCFG 3F690F02, 003C (r1 INTEL CALISTGA 6040000 LOHR 5A)
[ 0.000000] ACPI: BOOT 3F690FD8, 0028 (r1 PTLTD $SBFTBL$ 6040000 LTP 1)
[ 0.000000] ACPI: APIC 3F690F70, 0068 (r1 PTLTD APIC 6040000 LTP 0)
[ 0.000000] ACPI: SSDT 3F689FDA, 064F (r1 SataRe SataPri 1000 INTL 20050624)
[ 0.000000] ACPI: SS...

Could you try testing with Hardy as I mentioned previously? Additionally is your BIOS up to date?

Brian Murray wrote:
> Could you try testing with Hardy as I mentioned previously?
> Additionally is your BIOS up to date?
>
>
yes, its up-to-date

i use hardy and i get the bug msg

No, I can't try with Hardy. I have gutsy gibbon and I am not interested in going to another unless I am sure that it will work. I have had to many problems when going to another ex edgy to feisty.

shadowh511 <email address hidden> wrote: Brian Murray wrote:
> Could you try testing with Hardy as I mentioned previously?
> Additionally is your BIOS up to date?
>
>
yes, its up-to-date

i use hardy and i get the bug msg

--
bios bug error w/ feisty fawn on toshiba satellite a135 s4527
https://bugs.launchpad.net/bugs/124956
You received this bug notification because you are a direct subscriber
of the bug.

---------------------------------
Never miss a thing. Make Yahoo your homepage.

You don't need to install Hardy to be able to test this particular bug - booting off the Live CD should reveal it.

oopie, I'll get it off of a fiesty livecd (been using the alternate
installer, live cd has some issues)

On Jan 8, 2008 11:27 AM, Brian Murray <email address hidden> wrote:

> You don't need to install Hardy to be able to test this particular bug -
> booting off the Live CD should reveal it.
>
> --
> bios bug error w/ feisty fawn on toshiba satellite a135 s4527
> https://bugs.launchpad.net/bugs/124956
> You received this bug notification because you are a direct subscriber
> of the bug.
>

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.