The RedHat 6 Technical Notes suggest to try to boot the kernel with the parameter
so you might try that. But it looks to me like you have broken hardware. If that kernel parm doesn't work I would lean toward a hardware problem.
Hello there!
I have a RS-6000 7043-140 machine with AIX version 4.1.5, that is
working for almost 8 years now. It has a tty monitor. My problem
started when I upgraded my machine to install a gxt250 graphics adapter
card together with a 15" AOC VGA Monitor, logitech keyboard and mouse, ... (2 Replies)
I have an ultra 10 system, and am trying to install and verify a previously cloned hard drive, to make sure it works, that it really is a duplicate of the hard drive currently on an other server, etc.
I plugged in this cloned hard drive as master, only drive in the system.
No network LAN... (2 Replies)
Hi, I have a Unix box running HP-UX 10.20 and it suddenly won't boot. Every time it goes down the boot checklist, it hangs on "NFS client subsystem" and just continues to say busy/wait. I have read something about the /etc/auto_master but don't quite understand what has to happen to fix it. ... (4 Replies)
Why is one of my blade hanging and does nothing after trying to boot from CD???
==================
I tried to press 1....JS20 does not support SMS menu
Here's what I see after 30 minutes...
-------------------------------------------------------------------------------
... (0 Replies)
Hi guys,
i explain my problem:
I've FC10 64bit installed on a server Dell R410.
When i boot the system with eth0 or eth1 linked (only one eth linked), all work fine and the system start normally.
When i boot the system with eth0 + eth1 linked,
the system hang when the rpcind service... (1 Reply)
Hi folks,
I had problems trying to install SCO OpenServer 6 on a PC with no floppy drive and a SATA CD drive.
Eventually after advice received on this forum last week, I adopted a different approach by fitting the LSI HBA RAID adapter and associated disks into an older PC that does have CD and... (4 Replies)
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (0 Replies)
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (1 Reply)
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (6 Replies)
Discussion started by: naveeng
6 Replies
LEARN ABOUT FREEBSD
proto
PROTO(4) BSD Kernel Interfaces Manual PROTO(4)NAME
proto -- Driver for prototyping and H/W diagnostics
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device proto
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
proto_load="YES"
DESCRIPTION
The proto device driver attaches to PCI devices when no other device drivers are present and creates device special files for all resources
associated with the device. The driver itself has no knowledge of the device it attaches to. Programs can open these device special files
and perform register-level reads and writes. As such, the proto device driver is nothing but a conduit or gateway between user space pro-
grams and the hardware device.
Examples for why this is useful include hardware diagnostics and prototyping. In both these use cases, it is far more convenient to develop
and run the logic in user space. Especially hardware diagnostics requires a somewhat user-friendly interface and adequate reporting. Nei-
ther is done easily as kernel code.
FILES
All device special files corresponding to a PCI device are located under /dev/proto/pci<d>:<b>:<s>:<f> with pci<d>:<b>:<s>:<f> representing
the location of the PCI device in the PCI hierarchy. A location includes:
<d> The PCI domain number
<b> The PCI bus number
<s> The PCI slot or device number
<f> The PCI function number
Every PCI device has a device special file called pcicfg. This device special file gives access to the PCI configuration space. For each
valid base address register (BAR), a device special file is created that contains the BAR offset and the resource type. A resource type can
be either io or mem representing I/O port or memory mapped I/O space (resp.)
EXAMPLES
A single function PCI device in domain 0, on bus 1, in slot 2 and having a single memory mapped I/O region will have the following device
special files:
/dev/proto/pci0:1:2:0/10.mem
/dev/proto/pci0:1:2:0/pcicfg
AUTHORS
The proto device driver and this manual page were written by Marcel Moolenaar <marcel@xcllnt.net>.
SECURITY CONSIDERATIONS
Because programs have direct access to the hardware, the proto driver is inherently insecure. It is not advisable to use this driver on a
production machine.
MISSING FUNCTIONALITY
The proto driver does not yet support interrupts. Since interrupts cannot be handled by the driver itself, they must be converted into sig-
nals and delivered to the program that has registered for interrupts.
In order to test the transmission or reception of data, some means of doing direct memory access (DMA) by the device must be possible. This
too must be under the control of the program. The details of how a program can set up and initiate DMA still need to be fleshed out.
Support for non-PCI devices has not been implemented yet.
BSD April 29, 2014 BSD