Sponsored Content
Full Discussion: fedora problem
Operating Systems Linux Gentoo fedora problem Post 302122903 by fachtnaroe on Friday 22nd of June 2007 12:12:58 AM
Old 06-22-2007
Pci Bug #81

Dear linuxuser,

I installed FC7 on an Acer Aspire 1503. I saw the same error and encountered sporadic boot and shutdown errors.

I tried ubuntu but couldn't get the graphics to work. I'm presently typing via FC6 on it's first boot - it has an earlier version of 'nash'. This might be relevant. I didn't see the error but the startup was too fast. I'll know soon.

I booted completly problem free with gentoo linux but didn't know where to take that next!

What I've discovered from searching the web is that there are a lot of posts about error BIOS BUG #81, followed by a differing 8-digit number in square brackets. The number may vary, but it's always BIOS BUG #81.

The platforms, hardware, numbers and efects vary. Do a search yourself and you'll see.

In my case with FC7 when the errors came, pressing a key on the keyboard would move the boot to the next stage; then the boot would pause until I generated another input, and so on. Like wise shutdown, where I almost always had to use the external switch to turn off on-board WiFi to complete the powerdown!

Like I said. Do a search and you'll discover it's a lot more prevalent than you might think.

Regards,
Fachtna.
 

10 More Discussions You Might Find Interesting

1. Linux

fedora core 2 selinux problem

in fedora core 2 with enforcing mode in selinux , why even as a root OS doesnt give permission to create any directory or file in /home ? (1 Reply)
Discussion started by: the.last.soul
1 Replies

2. Shell Programming and Scripting

Urgent problem with SIGCONT and Fedora 4 :(

Hello, I stop a process with kill -s SIGSTOP, but when I try to restart it with kill -s SIGCONT it do nothing. I use Fedora Core 4. Thank you a lot (1 Reply)
Discussion started by: Nene
1 Replies

3. Linux

fedora core 6 problem

hi all i am currently using fedora core 3 . i downloaded the iso image of fedora core 6 but after installing the fedora core 6 . while starting linux it gives a error saying init is been killed . wht is happened? thank u (3 Replies)
Discussion started by: nageshrk
3 Replies

4. Programming

problem with accept() on Fedora 8

hi, accept() seems to be still blocking after socket is being closed on our Fedora 8 build. not sure if this is a common problem because i have never experienced this on any other platforms, however i have seen someone else having this issue on Redhat 7 and 9. so is there a socket option fedora... (10 Replies)
Discussion started by: Akimaki
10 Replies

5. Linux

Problem about Fedora directory permission

Problem about Fedora directory permission,can anyone help me? In fedora,I have two ordinary user named user1&user2 in different groups,when I logined user1 and created a dir named test/ in '/home/ user1/',and do 'chmod 750 test',so when 'ls -l',it appears 'drwxr- x---' for 'test',but when I... (3 Replies)
Discussion started by: zhouq3132
3 Replies

6. Red Hat

Problem installing perlcc in fedora 9

Hi guys i installed fedora 9 in my system. i installed perl-devel rpm and perl-5.10.0 rpm. But perlcc not in /usr/bin/ directory.But perl,perldoc binaris installed. i am new one for linux. (3 Replies)
Discussion started by: viveksnv
3 Replies

7. SuSE

Fedora 9 problem

I appeal to all those of you that have experience with Fedora 9 for help. I am trying to install a suite of software which tries to make changes to the /etc/dhcpd.conf file. After the changes have been made the dhcpd service will not start and the original conf file is restored. However dhcpd... (1 Reply)
Discussion started by: johnf
1 Replies

8. Linux

Problem mounting extern hd (fedora 9)

Hi there, I'm having a bit of a strange problem which I would appreciate some help with. The Problem: I have two external hard drives, but I'm borrowing one off my parents to copy data too (one of mine, which is identical to theirs - WD MyBook 300g - is on its way out). Fedora 9 recognizes... (3 Replies)
Discussion started by: lasthidingplace
3 Replies

9. Red Hat

Problem booting Fedora 11 x86_64

Hi, I am having booting issue with Fedora 11 x86_64 (64-bit version) on my laptop. Laptop configuration is as below: OS : Windows Vista Home Premium (64-bit) Processor : Intel Core 2 Duo T6400 2.0 GHz RAM : 4 GB Tried following different way for installation: 1. Installed Fedora 11 on... (2 Replies)
Discussion started by: r2kv2k
2 Replies

10. Linux

Problem with CRONTAB on Fedora and CentOS

Hello, Can anyone please explain HOW Crontab i.e. job scheduling daemon works in Fedora and CentOS or any Linux platform(Ubuntu).... What are the points that i have to take care of if have to include a script to be run at a specific scheduled time. URGENT reply requested. Please help (1 Reply)
Discussion started by: Vabiosis
1 Replies
BIOSDEVNAME(1)						      General Commands Manual						    BIOSDEVNAME(1)

NAME
biosdevname - give BIOS-given name of a device SYNOPSIS
biosdevname [options] [args]... DESCRIPTION
biosdevname takes a kernel device name as an argument, and returns the BIOS-given name it "should" be. OPTIONS
-i, --interface Treat [args] as ethernet devs -d, --debug Enable debugging -p, --policy [physical|all_ethN] -P, --prefix [string] string use for embedded NICs in the physical policy (default=em) -x, --nopirq Do not use $PIR table for mapping PCI device to slot. Some BIOS have incorrect values. -s, --smbios [x.y] Require minimum SMBIOS version x.y POLICIES
The physical policy is the current default. However, when invoking biosdevname in udev rules, one should always specify the policy you want, as the default has changed over time. The physical policy uses the following scheme: em<port>[_<virtual instance>] for embedded NICs p<slot>p<port>[_<virtual instance>] for cards in PCI slots The all_ethN policy makes a best guess at what the device order should be, with embedded devices first, PCI cards in ascending slot order, and ports in ascending PCI bus/device/function order breadth-first. However, this policy does not work if your PCI devices are hot-plugged or hot-pluggable, including the virtual functions on an SR-IOV device. In a hot-plug scenario, each separate udev instance will be invoked in parallel, while the device tree is still being populated with new devices. Each udev instance will see a different PCI tree, and thus cannot provide consistent enumeration. Use of this policy should be limited to only scenarios where all PCI devices are present at boot (cold-plug). EXIT CODES
Returns 0 on success, with BIOS-suggested name printed to stdout. Returns 1 on provided device name lookup failure. Returns 2 if system BIOS does not provide naming information. biosdevname requires system BIOS to provide naming information, either via SMBIOS or sysfs files. Returns 3 if not run as root but requires root privileges. Returns 4 if running in a virtual machine. SEE ALSO
http://linux.dell.com/wiki/index.php/Oss/libnetdevname http://linux.dell.com/files/biosdevname/ git://linux.dell.com/biosdevname.git RELATED PROGRAMS
The dmidecode package contains two tools useful for debugging BIOS features that biosdevname uses, specifically dmidecode to read the SMBIOS Type 9 and Type 41 tables, and biosdecode to read the PCI IRQ Routing Table. Please include the output of each of these programs in any bug reports. AUTHOR
biosdevname was written by Matt Domsch <Matt_Domsch@dell.com> This manual page was written by Rudy Gevaert <Rudy.Gevaert@UGent.be>, for the Debian project (but may be used by others). Nov 28, 2010 BIOSDEVNAME(1)
All times are GMT -4. The time now is 03:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy