Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Device Probe freezes after detecting Ethernet address while installing FreeeBSD 7.0 Post 302274355 by ideogon on Wednesday 7th of January 2009 12:13:22 PM
Old 01-07-2009
Progress...sort of

I've actually been able to get past this part once. It continued into the installation menu. I was able to configure the system and then when I set it to boot from the CD/DVD, it said that the CD/DVD drive isn't supported.

Did some Googling and apparently that even though the BIOS recognizes my DVD (and thus loaded the installation menu from it) doesn't mean that the FreeBSD installation recognizes my DVD drive. According to FreeBSD's site, it should recognize any ATAPI CD/DVD drive, which it is according to the BIOS. I went back into the BIOS and realized that the drive was being recognized, however, as slave and not master, so I reconnected it as slave (confirmed this in the BIOS) and rebooted, speculating that this is the underlying issue of FreeBSD not supporting my CD/DVD drive.

However, now I cannot get past this point (after probing the Ethernet address) in the device probe in order to continue on to the FreeBSD installation menu.

Any ideas...?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Ethernet Address?

How do I find my ethernet address (HostID) under OS X in the terminal? (2 Replies)
Discussion started by: Dimyas
2 Replies

2. Programming

PCI device probe and find

:confused: Hi, everybody. Pleeeeese HLP!!! I write PCI device driver for bridge controller PCI-VME bus in freeBSD 2.2. And firs run function probe(): static char* probe(tag, type). Whuy probe() don't work for my vendorID and deviceID (bridge controller and videoadapter). But... (1 Reply)
Discussion started by: Alex_T
1 Replies

3. IP Networking

How to Achive IP address through MAC(Ethernet) address

Hi sir, i want to make such programe which takes MAC(Ethernet) address of any host & give me its IP address....... but i'm nt getting that how i can pass the MAC address to Frame........ Please give me an idea for making such program... Thanks & regards Krishna (3 Replies)
Discussion started by: krishnacins
3 Replies

4. BSD

PROBE not find the device ID

Hi All, Probe is not returning the Device ID, while device (PCI Express-to-PCI Bridge) is already detected by "lspci". I checked this with printing all the device ID which has been detected. Can anyone give me any suggestion or solution. Thanks (in advance) Appu (2 Replies)
Discussion started by: appu
2 Replies

5. Linux

Do linux have a device file for ETHERNET CARD.

Sir, Do linux have device file for ethernet card. Can I use open , read , write , system calls to read data transferred through LAN. Is there any methods to read network datas (with out header and tailor information). Hope anyone can help me out. Thanking you.... ... (5 Replies)
Discussion started by: iamjayanth
5 Replies

6. Shell Programming and Scripting

Detecting A USB Storage Device From A Script

I need a way to reliably detect a USB storage device from a bash script. I know how to use 'lsusb' to list the USB devices - but then how can I match a device listed in 'lsusb' output to an actual disk device? Is there some way to map one to the other? Any help appreciated. (3 Replies)
Discussion started by: dmaddox099
3 Replies

7. Solaris

Get ethernet address

Hi, How do I get ethernet (mac) address of all the interfaces (including the unplumbed interfaces) ? I do not want to use ifconfig -a plumb and unplumb. Looking for some other ways. Even c program will help. I am looking for S9 as well as S10. So dladm also wont work as it is only for S10 ... (2 Replies)
Discussion started by: patjones
2 Replies

8. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

9. Red Hat

Ethernet Port device path?

Hi, I have a server program that reads data coming in on USB ports. Device paths are in the format: /dev/ttyUSB0 Now, I would like to log data from another device coming in over Ethernet. My first step is trying to track down what the correct device path is which I am unsure of. Anyone... (9 Replies)
Discussion started by: fedora18
9 Replies

10. UNIX for Advanced & Expert Users

C program to detect duplicate ip address if any after assigning ip address to ethernet interface

Hi , Could someone let me know how to detect duplicate ip address after assigning ip address to ethernet interface using c program (3 Replies)
Discussion started by: Gopi Krishna P
3 Replies
BOOT0CFG(8)						    BSD System Manager's Manual 					       BOOT0CFG(8)

NAME
boot0cfg -- boot manager installation/configuration utility SYNOPSIS
boot0cfg [-Bv] [-b boot0] [-d drive] [-e bell character] [-f file] [-i volume-id] [-m mask] [-o options] [-s slice] [-t ticks] disk DESCRIPTION
The FreeBSD 'boot0' boot manager permits the operator to select from which disk and slice an i386 machine (PC) is booted. Note that what are referred to here as ``slices'' are typically called ``partitions'' in non-BSD documentation relating to the PC. Typi- cally, only non-removable disks are sliced. The boot0cfg utility optionally installs the 'boot0' boot manager on the specified disk; and allows various operational parameters to be con- figured. On PCs, a boot manager typically occupies sector 0 of a disk, which is known as the Master Boot Record (MBR). The MBR contains both code (to which control is passed by the PC BIOS) and data (an embedded table of defined slices). The options are: -B Install the 'boot0' boot manager. This option causes MBR code to be replaced, without affecting the embedded slice table. -b boot0 Specify which 'boot0' image to use. The default is /boot/boot0 which will use the video card as output, alternatively /boot/boot0sio can be used for output to the COM1 port. (Be aware that nothing will be output to the COM1 port unless the modem signals DSR and CTS are active.) -d drive Specify the drive number used by the PC BIOS in referencing the drive which contains the specified disk. Typically this will be 0x80 for the first hard drive, 0x81 for the second hard drive, and so on; however any integer between 0 and 0xff is acceptable here. -e bell character Set the character to be printed in case of input error. -f file Specify that a backup copy of the preexisting MBR should be written to file. This file is created if it does not exist, and replaced if it does. -i volume-id Specifies a volume-id (in the form XXXX-XXXX) to be saved at location 0x1b8 in the MBR. This information is sometimes used by NT, XP and Vista to identify the disk drive. The option is only compatible with version 2.00 of the 512-byte boot block. -m mask Specify slices to be enabled/disabled, where mask is an integer between 0 (no slices enabled) and 0xf (all four slices enabled). Each mask bit enables corresponding slice if set to 1. The least significant bit of the mask corresponds to slice 1, the most sig- nificant bit of the mask corresponds to slice 4. -o options A comma-separated string of any of the following options may be specified (with ``no'' prepended as necessary): packet Use the disk packet (BIOS INT 0x13 extensions) interface, as opposed to the legacy (CHS) interface, when doing disk I/O. This allows booting above cylinder 1023, but requires specific BIOS support. The default is 'packet'. setdrv Forces the drive containing the disk to be referenced using drive number definable by means of the -d option. The default is 'nosetdrv'. update Allow the MBR to be updated by the boot manager. (The MBR may be updated to flag slices as 'active', and to save slice selection information.) This is the default; a 'noupdate' option causes the MBR to be treated as read-only. -s slice Set the default boot selection to slice. Values between 1 and 4 refer to slices; a value of 5 refers to the option of booting from a second disk. The special string ``PXE'' or a value of 6 can be used to boot via PXE. -t ticks Set the timeout value to ticks. (There are approximately 18.2 ticks per second.) -v Verbose: display information about the slices defined, etc. FILES
/boot/boot0 The default 'boot0' image /boot/boot0sio Image for serial consoles (COM1,9600,8,N,1,MODEM) EXIT STATUS
The boot0cfg utility exits 0 on success, and >0 if an error occurs. EXAMPLES
To boot slice 2 on the next boot: boot0cfg -s 2 ada0 To enable just slices 1 and 3 in the menu: boot0cfg -m 0x5 ada0 To go back to non-interactive booting, use fdisk(8) to install the default MBR: fdisk -B ada0 SEE ALSO
geom(4), boot(8), fdisk(8), gpart(8) AUTHORS
Robert Nordier <rnordier@FreeBSD.org> BUGS
Use of the 'packet' option may cause 'boot0' to fail, depending on the nature of BIOS support. Use of the 'setdrv' option with an incorrect -d operand may cause the boot0 code to write the MBR to the wrong disk, thus trashing its previ- ous content. Be careful. BSD
October 1, 2013 BSD
All times are GMT -4. The time now is 07:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy