Sponsored Content
Operating Systems Solaris Solaris 10 crashes upon boot after TUN driver installed Post 302456386 by TomSu on Friday 24th of September 2010 05:59:34 AM
Old 09-24-2010
Solaris 10 crashes upon boot after TUN driver installed

Hey!
I compiled TUN 1.1 driver on my Solaris 10 64bit, and everything was working fine, all the commands for installation were successfull (add_drv, devfsadm -i tun ... etc.)
and the driver was working fine as I got OpenVPN server up and running with successful clients attached. My only problem is that when I reboot the system now it will crash and instantly reboot again... and again in the neveredning loop until I boot failsafe, mount the root file system and remove this tun driver from /usr/kernel/drv/amd64/
Then the system boots fine and I can install again the driver and use it. Until next reboot of course ;-)
Any hints for me what could have I missed ?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Samba crashes on Solaris with Veritas Cluster

We recently transferred our Samba server to a cluster of two Sun systems running Solaris 9 with Veritas Cluster Server. We used Samba 3.0.7. Since then Samba seems to crash every 2 to 3 days, always around noon. The symptoms are that at first people who are connected lose the ability to access... (1 Reply)
Discussion started by: rhfrommn
1 Replies

2. Red Hat

How to know whether the network driver alredy installed in my system

I am using NVIDIA nforce: Networking controllers And Redhat enterprice linux ws version 4 32 bit: OS I want to connect my system to Broadband internet using linux. From where can I download the driver for nertwork. How to know whether the network driver alredy installed in my system. ... (0 Replies)
Discussion started by: rijas
0 Replies

3. AIX

how to know if my aix have multi-path driver installed?

I have an aix server, it is not a VIO server or client. I need to check if it has multi-path driver installed, how to check it? (1 Reply)
Discussion started by: rainbow_bean
1 Replies

4. Shell Programming and Scripting

Boot time driver conflict

I have a Microdia web cam. Some times it won't work if and only if there is a "HV7131R image sensor detected" statement in the boot up. In this case when I try to get a .png snapshot all I get is a frame full of what appears to be white noise only it is mostly green. Here is the command I am... (0 Replies)
Discussion started by: slak0
0 Replies

5. Solaris

Xsun hangs crashes with TSI card in Solaris 10

Upgrading from Solaris 8 to Solaris 10 on 40+ workstations -- desktop Unix Sparc systems of various ilk: Netra T1, Sunblade-100, Sunfire. Many of these systems are not meant for the desktop, but we've installed TSI cards like GFX-400, GFX-200 series cards for multi-head operation. This is the... (0 Replies)
Discussion started by: paz9
0 Replies

6. Red Hat

How to verify the current NIC driver version installed in RHEL5.3??

Guys, Can you help me how to verify the current installed NIC driver version in RHEL5.3? Thanks.:D (1 Reply)
Discussion started by: shtobias
1 Replies

7. UNIX for Dummies Questions & Answers

boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd

Help, suspect hacked via serial or electric! any ideas on error "Pid:1, comm:swapper Tainted:G W 2.6.35-22 generic #33 -unbutu device = "(null)" or unknown-blocklist(8.1) please append a correct "root"boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd. Thanks... (3 Replies)
Discussion started by: kryclear
3 Replies

8. Solaris

Frequent crashes in ESXi virtual Solaris machine

Anybody have any ideas on what could be causing this crash? This an x86 virtual machine I have running in ESXi at my house, so obviously no way to send the data to Oracle for analysis. Just curious if anyone has any ideas. I suspect motherboard problems with the x86 hardware, as I already... (4 Replies)
Discussion started by: christr
4 Replies

9. OS X (Apple)

MacOS 10.15 Catalina Crashes and Freezes on Boot

Sadly, I have turned off my access to the Apple Developers Beta program after installing macOS 10.15 Catalina a few days ago. After the install, I rebooted by MacBook Air and it "hard froze" and we were heading out of town so I grabbed a backup MBA running Mojave. Then, after getting back at... (10 Replies)
Discussion started by: Neo
10 Replies

10. OS X (Apple)

Warning! Upgrade to Catalina 10.15.3 Crashes MacPro (2013) - Will Not Boot !

WARNING! Just upgraded my MacPro (2013) from Catalina 10.15.2 to 10.15.3. After the routine download and restart for upgrade installation, the Mac would not boot. Totally crashed. Now, I'm in the process of a 15 hour restore from my last time machine backup. I'm not very happy with... (3 Replies)
Discussion started by: Neo
3 Replies
drvconfig(1M)						  System Administration Commands					     drvconfig(1M)

NAME
drvconfig - apply permission and ownership changes to devices SYNOPSIS
drvconfig [-bn] [-a alias_name] [-c class_name] [-i drivername] [-m major_num] [-r root_dir] DESCRIPTION
devfsadm(1M) is now the preferred command and should be used instead of drvconfig. The default operation of drvconfig is to apply permission and ownership changes to devices. Normally, this command is run automatically after a new driver has been installed (with add_drv(1M)) and the system has been rebooted. OPTIONS
The following options are supported: -aalias_name Add the name alias_name to the list of aliases that this driver is known by. This option, if used, must be used with the -m major_num, the -b and the -i drivername options. -b Add a new major number to name binding into the kernel's internal name_to_major tables. This option is not normally used directly, but is used by other utilities such as add_drv(1M). Use of the -b option requires that -i and -m be used also. No /devices entries are created. -cclass_name The driver being added to the system exports the class class_name. This option is not normally used directly, but is used by other utilities. It is only effective when used with the -b option. -idrivername Only configure the devices for the named driver. The following options are used by the implementation of add_drv(1M) and rem_drv(1M), and may not be supported in future versions of Solaris: -mmajor_num Specify the major number major_num for this driver to add to the kernel's name_to_major binding tables. -n Do not try to load and attach any drivers, or if the -i option is given, do not try to attach the driver named drivername. -rroot_dir Perform operations under root_dir, rather than directly under root. EXIT STATUS
0 Successful completion. non-zero An error occurred. FILES
/devices Device nodes directory /etc/minor_perm Minor mode permissions /etc/name_to_major Major number binding /etc/driver_classes Driver class binding file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
sh(1), add_drv(1M), modinfo(1M), modload(1M), modunload(1M), rem_drv(1M), update_drv(1M), path_to_inst(4), attributes(5), devfs(7FS) SunOS 5.10 9 Aug 2004 drvconfig(1M)
All times are GMT -4. The time now is 09:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy