SCSI Emulation for IDE Tape Devices

Linux has a nifty driver called ide-scsi.o, an SCSI emulation for IDE devices, that allows SCSI commands to sent to IDE devices. These IDE devices (CDROM, tape drives, etc...) appear as SCSI devices.
Does Solaris have something similiar?
Thanks,
Quang

legal wrote:
I have tried burning without setting scsi emulation but give me some errors, so how can I set scsi emulation for burning CD/DVD on k3b???
It's in rc.conf by adding "ide-scsi"???
I'm using Kernel 2.6.4 (IDE version), KDE 3.2.1 and K3b 0.11.6.
Note: I've tried to upgrade k3b from 0.11.6 to 0.11.7 with "pacman -Su k3b" but say to me that already in last version - 0.11.6.
with kernel 2.6 you don't need anymore scsi emulation for cd burning, i do that, on the bootloader ( lilo is what i use) i add at the append line this --> hdc=ide-cd , and that's all, maybe even that is not needed, not sure. If you want to test if that works open a shell and type --> cdrecord --dev=ATAPI --scanbus
It should show your burner.
For k3b you maybe need to run the setup program first, and make sure your cdrdao is uptodate.

Similar Messages

How do I set up an emulator for testing my application?

I'm starting to wade into GPIB and cannot seem to find the best way to continue given all the components (not meaning ActiveX) required to assemble a semi-reliable development and testing environment for beta rollouts.
I have set up my design environment. Now I need a way to emulate some of the equipment I will be developing for so that I may test my apps before final testing on the actual equipment (which I obviously have no access to at this point).
Given that.. am I correct in understanding that LabView or IVI allows this type of functionality? If so, here are my specific questions regarding development:
1) Do I currently need any hardware or can the GPIB device list be populated from IVI/LabView emula
tors? In other words... how do I make the 'link' between these two technologies?
2) Can IVI/LabView run on the same machine as my test application, or is a secondary machine required?
3) Is there a general punch list of software (LabView, etc.) I might need in order to get this going?
4) Any general (or specific) overviews that may help me get over this hump would be greatly appreciated.
Charles

Whether or not you are able to simulate your hardware will depend on what method you are using to program it. If you are programming the instrumentation directly using the GPIB ActiveX control or GPIB calls directly you will not have the ability to do simulate in software. If you are using an instrument driver, however, you will be able to do simulation if the instrument driver is IVI compliant.
Assuming that you are using an IVI-compliant instrument driver, here are the answers to your questions:
1. You do not need any hardware whatsoever. You can either specify to use simulation in your code by using the InitWithOptions functionality and specifying "SIMULATE=TRUE" in the option string parameter. You can also set things up externally so that you can alter simulation strictly through the IVI configuration so that your code doesn't have to change.
2. It will run on the same machine as your code. As far as your application is concerned, it will not appear any differently however no GPIB communication will occur.
3. IVI compliant instrument drivers for all of the GPIB hardware you are using. These are available for download from ni.com.
4. I think that there may be some IVI-related application notes.
Assuming that you are not using an IVI-compliant instrument driver and instead are either using a non-IVI instrument driver or making GPIB calls directly, things can get a little more elaborate. If you want full emulation capability you'll need to write another piece of software that emulates your device. This can be done in LabVIEW or any other ADE of your choice. What you'll need is a second GPIB card (to act as your device) that you'll cable to from your main computer. That card can live in a second machine or in the same one as your main application. You may want to put it in a separate test machine just to keep things a little cleaner.
If you go with this approach, it's not too difficult to write an emulator for a single device (or at least that functionality of a device that you use) per GPIB card. It will be more difficult to write an emulator that emulates multiple devices using a single GPIB card. In other words, you may want to use a separate GPIB card for each instrument you want to emulate. I wrote such an emulator some time ago but can't seem to find it. In any case, it's probably only a couple of days effort.
To make a long story short, your life will be a lot easier if you have IVI-compliant instrument drivers available for the hardware that you are using.
Jason

Scsi-emulation

A couple of newb questions:
1) what is scsi -emulation and why does XCDRoast need it?
2)do i need to setup scsi-emulation for all cd burning apps or are there any apps that will work without it?
3) how do i setup scsi emulation?
Thanks for the help in advance,
Mike

dk wrote:cdrecord dev= "ATAPI:0,1,0" gracetime=2 fs=4096k driveropts=burnfree,noforcespeed -v -useinfo speed=52 -dao -eject -pad -audio /home/dk/music/something.wav
well after you have all the .wavs setup in the directory you will be burning from that command should work except instead of "something" use the "*" wildcard. for example:
cdrecord dev= "ATAPI:0,1,0" gracetime=2 fs=4096k driveropts=burnfree,noforcespeed -v -useinfo speed=52 -dao -eject -pad -audio /home/dk/music/*.wav
the * means, of course that anything that ends in .wav will be burned.

Why maintain separate kernels for ide / scsi?

I don't really understand why arch has separate kernels for ide and scsi. I was just reading some forum posts about difficulties in installing arch, and they are all related to SATA. Apparently, you need to boot the CD with the non-default scsi kernel in order to get sata drives recognized for installation.
Also, people are expecting to be using their USB storage devices, which all require SCSI, but apparently this isn't well known, judging by the number of posts asking for help on this matter.
I hope we can discuss this issue here, and hopefully make changes for the Wombat install CD.
The SCSI kernel is only a ~600kb larger download than the default IDE, so I don't think the reason for separating them is based on size. Is the kernel bootup time difference really noticable on an i686 system? (ie, people running arch don't have such old computers where it would be a big deal)
If there are legitimate reasons for keeping an ide-only kernel, then I suggest we at least make SCSI the default, and provide kernel26-noscsi as an option for those who need it. But I would personally prefer to get rid of the ide-only kernel alltogether.

paranoos wrote:Also, people are expecting to be using their USB storage devices, which all require SCSI, but apparently this isn't well known, judging by the number of posts asking for help on this matter.
USB storage devices work very well with the IDE kernel just by loading a few kernel modules (2 as far as I remember) or use hotplug. It worked out of the box for me. Read the Wiki for this.
About the SATA installation problem, maybe a Wiki page (or some lines in the online installation guide) about this would be useful. I plan buying a SATA HDD (with a new PC) soon and I am still thinking wether Arch will install on it without no problem.

RMAN backup in HP Ultrium 3-SCSI(3mn) tape device

Dear All
IS it possible to take online RMAN backup in HP Ultrium 3-SCSI(3mn) tape device?
Note: this is not a tape library, a stand alone tape device.
Thanks & Regards
Quazi Abdur Rab

In RAC, Please note that you can take backup from any node and you can able to restore from any node.
If you taking backup to disk then you must mount the same backup mount on both servers in order to able to backup and restore.
In your case you are taking backup to FRA and from there taking to tape.
The TSM wtih tdop agent is congiured on Node1 and not on Node 2 thats why you are not able to restore from node2.
27029, 00000, "skgfrtrv: sbtrestore returned error"
// *Cause: sbtrestore returned an error. This happens when retrieving a
// backup file during a restore operation.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
/u01/home/oracle:DBA>
If you restore from FRA or using RMAN both nodes know the backup location and able to restore.
Hope this helps,
Regards
http://www.oracleracexpert.com
Cross platform Transportable tablespace using RMAN
http://www.oracleracexpert.com/2009/10/cross-platform-transportable-tablespace.html
Duplicate RAC Database using RMAN
http://www.oracleracexpert.com/2009/12/duplicate-rac-database-using-rman.html

SCSI ID for a Quantum FB10A011 IDE HDD

I took my old Performa apart to salvage the HDD, I want to find out what's on it.
I hooked it up to my Beige G3 MT but it won't show it even being there on the desktop. Is there a SCSI ID for the FB10A011 or will it even work in my Beige.
Mic

What volumes does the Startup Disk control panel show? Is the SCSI cable you mentioned attached to the logic board where the ATA cables attach, or to a PCI expansion card?
As you have a collection of drives and cables, we need to find out the ROM Revision of your logic board. This assumes you have OS9 on the machine as your profile suggests.
1) Make sure you are booted into OS9 on a local drive (not a CD)
2) From the Apple Menu, launch Apple System Profiler (ASP).
3) Toward the bottom of the first page is a section labeled "Production Information." If necessary, click on the little disclosure arrow to expand that section.
4) Once expanded, you will see one entry is "ROM Revision' followed by a code:
Code $77D.40F2 is ROM Rev 1
Code $77D.45F1 is ROM Rev 2
Code $77D.45F2 is ROM Rev 3
In OS 8 and 9, Rev 1 machines can have only ONE ATA device per ATA cable; Rev 2 and 3 machines can have up to TWO ATA devices per cable. Figure out your ROM rev before trying anything else so we know what we're fighting.
While in ASP, click on the second tab, "Devices and Volumes" and see if the info there agrees with what you have installed. Often any master/slave confusion will show up there.
Sometimes, adding hardware to the Beige G3 requires a CUDA reset or at least a PRAM zap to get the new device properly polled and recognized. If you need help on how to do either, post back.
When I researched your drive on the Seagate site (they bough both Quantum and Maxtor) I could not find specific information on your drive number. The chart I linked was their generic jumper chart that was supposed to include Fireball drives. However, they have different series of drives with minor variants so you need to search the site yourself with the drive at hand to see any minor name or model info on the label. I believe they may not be providing data for such old drives. However, having the label in front of you may help.
A

Device Emulator for BE3000

The device emulator for the UC320 is a great tool. Do we have one for the BE3000? Is the BE3000 the same code base as the UC320?
Most small business owners have multiple companies under one roof. I note in teh UC320 I was not able to have a different auto attendant for a different DID? Do we expect to do this in the BE3000?
Thanks -

There is no device emulator for BE3000. We have talked about creating one, so will get back when it is available.
BE3000 is not same code base as UC320, it is based on CUCM code base.
We are looking to add multiple Autoattendants in a follow-up release. How many AAs do u think should be supported?
Thanks

HT5621 I have several apple devices, three are mine and the other ones belong to my little children. I use the same ID and password for all the devices. Is this a good idea? Do I need to change the apples ID?

I use the same apple ID for all my devices, 2 iphones, 2 itouch, 1 macbook pro, 2 ipads. Becuse I have small children, can I change that and still, have control, and don´t need to buy the same things serveral times.

It is something I would avoid if possible. I would want to educate my children to think possessively and therefore of security. Yes, I know you are all family but at the end of the day you wouldn't want your children to be blaming each other for any problems that arise. Well, that's how I see it, for what it is worth.

Add tape device to non-global zone

Hi,
I have a SCSI attached Ultrium tape device attached and configured against the global zone.
The /dev/rmt/0* definitions in the global zone are links to ../../devices/pci@2*
I need to be able to use this tape device from the non-global zones.
To enable this, I have done the following:
zonecfg -z <zone name>
add device
set match=/dev/rmt/0
end
verify
commit
exit
I repeated the above for /dev/rmt/0m and /dev/rmt/0mn
Then I restarted the zone with the command:
zoneadm -z <zone name> reboot
After the reboot, I can see the device when using "mt -f /dev/rmt/0 status", but whenever I try to write a SAP brbackup to the new (initialised and not write protected) tape within the drive I get the following error:
BR0278E Command output of 'LANG=C cd /oracle/<SID>/sapbackup && /usr/sap/<SID>/SYS/exe/run/brtools -f detach LANG=C cpio -iuvB .tape
sh: /dev/rmt/0mn: cannot open
BR0280I BRBACKUP time stamp: 2012-04-04 08.21.41
BR0279E Return code from 'LANG=C cd /oracle/<SID>/sapbackup && /usr/sap/<SID>/SYS/exe/run/brtools -f detach LANG=C cpio -iuvB .tape.
BR0359E Restore of /oracle/<SID>/sapbackup/.tape.hdr0 from /dev/rmt/0mn failed due to previous errors
Have I created the device incorrectly, or does anyone have any ideas what could be the reason the write fails?
Any help appreciated.
Edited by: user11329299 on 04-Apr-2012 01:09

Hi,
Just to bring you up to speed, I have now fixed the issue.
The resolution was all within the iniSID.sap file that the backup is using. I have changed a number of parameters within this file:
1.     tape_copy_cmd = dd (was cpio)
2.     rewind = "mt     -f $ rew; sleep 30" (was " mt -f $ rew")
3.     rewind_offline = "mt -f $ offline; sleep 30" (was "mt -f $ offline")
4.     tape_pos_cmd = "mt -f $ fsf $: sleep 30" (was "mt -f $ fsf $")
5.     tape_size = 500G (was 18000M)
After making those changes, the backup started from within DB13. I believe that the main culprit was the tape_copy_cmd, but the others were changed to allow the tape drive time to become online again after any query.

Mac OS 10.4.10 and Tape Devices issues

Subject: [BRUServer-Announce] Mac OS X 10.4.10 Announcement...
I am posting this message out to the group for additional knowledge on
this issue..
We have a older G5 XServe with XRaid connected via Fibre Channel and an Adic
Scalar 100 LTO-2 tape unit connected via SCSI.
We have been seeing some issue with our tape unit lately and looking for
suggestions on a fix or work-a-round.
BRU suggest this:
<snip>
To resolve this issue, we strongly suggest that you downgrade to
10.4.8, as 10.4.9 has been known to exhibit the same type of symptoms.
<snip>
My question would be if we select to downgrade to Mac OS 10.4.8,
What would be the Best method to do downgrade to Mac OS 10.4.8 ?
Regards,
Roger Sinning
 PrePress System Administrator
Schmidt
Byron, MN 55920
schmidt
print solutions that deliver.
------ Forwarded Message
From: <[email protected]>
Reply-To: <[email protected]>
Date: Tue, 23 Oct 2007 17:32:54 -0700
To: <[email protected]>
Subject: [BRUServer-Announce] Mac OS X 10.4.10 Announcement...
Please do not reply to this message.
This list is for announcements only.
An Important Note for Mac Users of BRU Technology Under Mac OS X
Since the release of 10.4.10, there are a number of issues that have
surfaced with writing to tape and disk devices. For this reason,
10.4.10 is not compatible with tape devices connected to Mac OS X
10.4.10 via SCSI, FireWire, USB, SAS, or Fibre-Channel.
This is not a BRU Server software problem, but rather an Apple Mac OS
X problem when using any type of software that communicates with tape
devices.
Other problems with XRAID, Xsan, and other disk devices communicating
over these channels may also be realized.
http://www.attotech.com/troublemac.html
http://knowledgebase.tolisgroup.com/?View=entry&EntryID=47
http://support.overlandstorage.com/jive/entry!default.jspa?cateforyID=7&exte
rnalID=6041&fromSearchPage=true
http://www.google.com/search?hl=en&rls=en&q=10.4.10backup+tapeissues&btnG=
Search
To resolve this issue, we strongly suggest that you downgrade to
10.4.8, as 10.4.9 has been known to exhibit the same type of symptoms.
We apologize that we did not make the announcement sooner, however, we
believed that 10.4.11, which fixes this problem, would be released
much sooner than now. As of this announcement, 10.4.11 has yet to be
released, nor has there been an announcement for its expected release
date.

an update on my client's situation:
os: server 10.4.11
scsi card: LSILogic Ultra320, 1.3.39.0 firmware
tape: exabyte 1x10 library, vxa172 tape drive
after a reboot, but still running 10.4.10, the tape drive appeared on the SCSI bus.
after installing the 10.4.11 update, the OS can't see the tape drive, but the library is. basically, that's no different than before the update.
does anyone have any ideas on how to scare the drive into reappearing? would unloading/reloading kexts help? the library is basically useless without the tape drive reliably recognized by the SCSI card.

SCSI card for a G5 or processor upgrade for a G4?

Hi all
Actually, this is a question that concerns the G5 and the G4 forum, but I decided to post it here first.
So, I have this old G4/400 PCI with an Adaptec 2930 SCSI card that I use for scanning slides with an Artix 4000t sclide scanner; this works fine, but the G4 is rather slow when it comes to using some features of the scanning software, such as removing scratches.
I've been thinking about buying a SCSI card for my G5 (Dual 1.8) for some time now, but I'm not sure what card I should go for; I'm not even sure if there are still cards for such an "old" device as the slide scanner (about 3 to 4 years old, no Ultrawide or something like that). And then there's the problem of the drivers for the card - how long will they be available, especially now that Apple is switching to Intel...?
The other possibility would be to buy a processor upgrade for the G4. I've seen some at OWC, and they seem to be less expensive than a SCSI card. The drawback of this solution is of course that I'll have to keep the G4 standing on my desk... on the other hand, I do know that the scanner will work perfectly with the G4.
The G5, on the other hand... it will be faster and easier, since I won't have to transfer the files for storage and editing, I could free some space on my desk,... but will it work? The G5 is running 10.4, I'm not sure if my current scanner driver is compatible... and what when 10.5 comes out...?
So I'm looking for a second, third, fourth... opinion:
What would you do? Get a SCSI card for the G5 or a processor upgrade for the G4? What SCSI card would you recommend?
TIA,
Tina

I've done some research on G5 and SCSI and scanners, and obviously, what I remembered was correct... making it work seems at least tricky, and maybe expensive too (if you've got to buy new scanning software and and..).
So I guess that's decided: No SCSI on the G5. Leaves the question, should I buy a processor upgrade card for the G4? Getting some dual G4 on eBay might be an option, but then, that would be another computer in my already crammed office, and I just can't throw the G4 away, it's one of the very first models...
I came by the idea of a processor upgrade because I just played around with an old Mac SE, which has an 68030 accelerator card installed, and this seems to work fine. Anyone has any experience with G3 /G4 upgrades (good or bad)?
Smokerz: Why would you not recommend an upgrade? Any bad experiences?
Tina

QEMU host-only networking using tap devices

I'm trying to setup host-only networking on my QEMU VM running Arch (actually, the Archiso; there is no Arch installation present yet). A short summary:
What I want
connect to the host from the guest system
connect to the guest from the host system
using a tap device (to avoid user-mode networking) on a network bridge (to connect guest and host)
Eventually, I want to run an AMP stack on the VM for web development. (Let's, for now, ignore the fact that I might need an internet connection later on to install packages)
What I tried
I first set up a tap device:
ip tuntap add dev tap0 mode tap
and then a network bridge:
BRIDGE='qemubr0'
brctl addbr ${BRIDGE}
brctl addif ${BRIDGE} tap0
ip link set up dev ${BRIDGE}
The relevant parameters I run QEMU with are:
qemu-system-x86_64 \
-net nic \
-net tap,ifname=tap0,script=no
QEMU starts without any errors, but trying to ping the host from within the VM results in:
-- VM:
# ping 10.0.2.2
connect: Network is unreachable
(FYI: 10.0.2.2 is supposed to be the default IP address of the host system (?) according to http://wiki.qemu.org/Documentation/Networking )
Relevant logs/outputs
dmesg on the host machine:
[ 0.339337] NET: Registered protocol family 2
[ 0.339670] TCP established hash table entries: 32768 (order: 6, 262144 bytes)
[ 0.339851] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
[ 0.340102] TCP: Hash tables configured (established 32768 bind 32768)
[ 0.340171] TCP: reno registered
[ 0.340182] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[ 0.340226] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[ 0.340327] NET: Registered protocol family 1
[ 0.340353] pci 0000:00:02.0: Video device with shadowed ROM
[ 0.341863] PCI: CLS 64 bytes, default 64
[ 0.341937] Unpacking initramfs...
[ 0.503984] Freeing initrd memory: 4908K (ffff88003765a000 - ffff880037b25000)
[ 0.504055] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 0.504060] software IO TLB [mem 0xb94a1000-0xbd4a1000] (64MB) mapped at [ffff8800b94a1000-ffff8800bd4a0fff]
[ 0.504112] Simple Boot Flag at 0x35 set to 0x1
[ 0.504352] microcode: CPU0 sig=0x1067a, pf=0x80, revision=0xa0c
[ 0.504364] microcode: CPU1 sig=0x1067a, pf=0x80, revision=0xa0c
[ 0.504475] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[ 0.504524] Scanning for low memory corruption every 60 seconds
[ 0.505041] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.505090] Initialise system trusted keyring
[ 0.505685] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.508836] zpool: loaded
[ 0.508841] zbud: loaded
[ 0.509100] VFS: Disk quotas dquot_6.5.2
[ 0.509170] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.509392] msgmni has been set to 7699
[ 0.509494] Key type big_key registered
[ 0.509767] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.509826] io scheduler noop registered
[ 0.509830] io scheduler deadline registered
[ 0.509893] io scheduler cfq registered (default)
[ 0.510198] pcieport 0000:00:1c.0: irq 24 for MSI/MSI-X
[ 0.510482] pcieport 0000:00:1c.1: irq 25 for MSI/MSI-X
[ 0.510705] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
[ 0.510713] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
[ 0.510744] pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
[ 0.510748] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
[ 0.510754] pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
[ 0.510785] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.510847] pciehp 0000:00:1c.0:pcie04: Slot #0 AttnBtn- AttnInd- PwrInd- PwrCtrl- MRL- Interlock- NoCompl- LLActRep+
[ 1.506690] tsc: Refined TSC clocksource calibration: 1396.499 MHz
[ 1.843356] pciehp 0000:00:1c.0:pcie04: Timeout on hotplug command 0x00000000 (issued 1333 msec ago)
[ 1.843368] pciehp 0000:00:1c.0:pcie04: service driver pciehp loaded
[ 1.843390] pciehp 0000:00:1c.1:pcie04: Slot #1 AttnBtn- AttnInd- PwrInd- PwrCtrl- MRL- Interlock- NoCompl- LLActRep+
[ 2.506739] Switched to clocksource tsc
[ 3.176680] pciehp 0000:00:1c.1:pcie04: Timeout on hotplug command 0x00000000 (issued 1333 msec ago)
[ 3.176691] pciehp 0000:00:1c.1:pcie04: service driver pciehp loaded
[ 3.176703] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 3.176768] vesafb: mode is 1440x900x32, linelength=5760, pages=0
[ 3.176770] vesafb: scrolling: redraw
[ 3.176774] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 3.176807] vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90004780000, using 5120k, total 5120k
[ 3.235921] Console: switching to colour frame buffer device 180x56
[ 3.294769] fb0: VESA VGA frame buffer device
[ 3.294803] intel_idle: does not run on family 6 model 23
[ 3.294882] GHES: HEST is not enabled!
[ 3.294990] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 3.316009] 0000:00:03.3: ttyS0 at I/O 0x1830 (irq = 17, base_baud = 115200) is a 16550A
[ 3.316238] Linux agpgart interface v0.103
[ 3.316307] rtc_cmos 00:02: RTC can wake from S4
[ 3.316496] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
[ 3.316535] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 3.316560] ledtrig-cpu: registered to indicate activity on CPUs
[ 3.316751] TCP: cubic registered
[ 3.316954] NET: Registered protocol family 10
[ 3.317338] NET: Registered protocol family 17
[ 3.317735] Loading compiled-in X.509 certificates
[ 3.317757] registered taskstats version 1
[ 3.318307] Magic number: 15:252:84
[ 3.318413] rtc_cmos 00:02: setting system clock to 2015-01-01 16:05:44 UTC (1420128344)
[ 3.318617] PM: Hibernation image not present or could not be loaded.
[ 3.320772] Freeing unused kernel memory: 1136K (ffffffff818e2000 - ffffffff819fe000)
[ 3.320775] Write protecting the kernel read-only data: 8192k
[ 3.324495] Freeing unused kernel memory: 748K (ffff880001545000 - ffff880001600000)
[ 3.326086] Freeing unused kernel memory: 336K (ffff8800017ac000 - ffff880001800000)
[ 3.336977] random: systemd-tmpfile urandom read with 4 bits of entropy available
[ 3.363462] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[ 3.372761] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 3.372934] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 3.379297] ACPI: bus type USB registered
[ 3.379343] usbcore: registered new interface driver usbfs
[ 3.379364] usbcore: registered new interface driver hub
[ 3.380595] usbcore: registered new device driver usb
[ 3.381344] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.381800] uhci_hcd: USB Universal Host Controller Interface driver
[ 3.381991] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[ 3.382003] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 3.382015] uhci_hcd 0000:00:1a.0: detected 2 ports
[ 3.382060] uhci_hcd 0000:00:1a.0: irq 20, io base 0x00001840
[ 3.382412] hub 1-0:1.0: USB hub found
[ 3.382427] hub 1-0:1.0: 2 ports detected
[ 3.383010] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[ 3.383021] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 2
[ 3.383032] uhci_hcd 0000:00:1a.1: detected 2 ports
[ 3.383073] uhci_hcd 0000:00:1a.1: irq 21, io base 0x00001860
[ 3.383523] hub 2-0:1.0: USB hub found
[ 3.383649] hub 2-0:1.0: 2 ports detected
[ 3.384187] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[ 3.384197] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 3
[ 3.384207] uhci_hcd 0000:00:1a.2: detected 2 ports
[ 3.384245] uhci_hcd 0000:00:1a.2: irq 22, io base 0x00001880
[ 3.384679] hub 3-0:1.0: USB hub found
[ 3.384693] hub 3-0:1.0: 2 ports detected
[ 3.385046] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 3.385056] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 4
[ 3.385067] uhci_hcd 0000:00:1d.0: detected 2 ports
[ 3.385104] uhci_hcd 0000:00:1d.0: irq 16, io base 0x000018a0
[ 3.385391] hub 4-0:1.0: USB hub found
[ 3.385405] hub 4-0:1.0: 2 ports detected
[ 3.386100] ehci-pci: EHCI PCI platform driver
[ 3.386149] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 3.386159] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 5
[ 3.386169] uhci_hcd 0000:00:1d.1: detected 2 ports
[ 3.386210] uhci_hcd 0000:00:1d.1: irq 17, io base 0x000018c0
[ 3.386499] hub 5-0:1.0: USB hub found
[ 3.386512] hub 5-0:1.0: 2 ports detected
[ 3.387422] ehci-pci 0000:00:1a.7: EHCI Host Controller
[ 3.387433] ehci-pci 0000:00:1a.7: new USB bus registered, assigned bus number 6
[ 3.387454] ehci-pci 0000:00:1a.7: debug port 1
[ 3.390536] SCSI subsystem initialized
[ 3.391377] ehci-pci 0000:00:1a.7: cache line size of 64 is not supported
[ 3.391407] ehci-pci 0000:00:1a.7: irq 23, io mem 0xf0805c00
[ 3.393114] libata version 3.00 loaded.
[ 3.400023] ehci-pci 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 3.400556] hub 6-0:1.0: USB hub found
[ 3.400572] hub 6-0:1.0: 6 ports detected
[ 3.420762] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 3.423437] hub 1-0:1.0: USB hub found
[ 3.423452] hub 1-0:1.0: 2 ports detected
[ 3.446764] hub 2-0:1.0: USB hub found
[ 3.446781] hub 2-0:1.0: 2 ports detected
[ 3.470096] hub 3-0:1.0: USB hub found
[ 3.470113] hub 3-0:1.0: 2 ports detected
[ 3.470446] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 3.470457] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
[ 3.470467] uhci_hcd 0000:00:1d.2: detected 2 ports
[ 3.470510] uhci_hcd 0000:00:1d.2: irq 18, io base 0x000018e0
[ 3.470855] hub 7-0:1.0: USB hub found
[ 3.470871] hub 7-0:1.0: 2 ports detected
[ 3.471114] ahci 0000:00:1f.2: version 3.0
[ 3.471277] ahci 0000:00:1f.2: irq 26 for MSI/MSI-X
[ 3.471324] ahci 0000:00:1f.2: SSS flag set, parallel bus scan disabled
[ 3.471354] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports 3 Gbps 0x1 impl SATA mode
[ 3.471359] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part ccc
[ 3.472602] scsi host0: ahci
[ 3.472778] scsi host1: ahci
[ 3.472926] scsi host2: ahci
[ 3.475424] scsi host3: ahci
[ 3.475545] ata1: SATA max UDMA/133 abar m2048@0xf0805000 port 0xf0805100 irq 26
[ 3.475549] ata2: DUMMY
[ 3.475551] ata3: DUMMY
[ 3.475553] ata4: DUMMY
[ 3.476505] ehci-pci 0000:00:1d.7: EHCI Host Controller
[ 3.476517] ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 8
[ 3.476540] ehci-pci 0000:00:1d.7: debug port 1
[ 3.480454] ehci-pci 0000:00:1d.7: cache line size of 64 is not supported
[ 3.480479] ehci-pci 0000:00:1d.7: irq 19, io mem 0xf0806000
[ 3.490041] ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 3.490373] hub 8-0:1.0: USB hub found
[ 3.490387] hub 8-0:1.0: 6 ports detected
[ 3.513423] hub 4-0:1.0: USB hub found
[ 3.513436] hub 4-0:1.0: 2 ports detected
[ 3.536764] hub 5-0:1.0: USB hub found
[ 3.536781] hub 5-0:1.0: 2 ports detected
[ 3.560098] hub 7-0:1.0: USB hub found
[ 3.560115] hub 7-0:1.0: 2 ports detected
[ 3.793361] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3.793627] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3.793633] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3.793664] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3.793670] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3.793788] ata1.00: ATA-8: TOSHIBA THNS128GG4BAAA-NonFDE, AGLA0203, max UDMA/100
[ 3.793792] ata1.00: 250069680 sectors, multi 16: LBA48
[ 3.794031] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3.794035] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3.794065] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3.794070] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3.794186] ata1.00: configured for UDMA/100
[ 3.794336] scsi 0:0:0:0: Direct-Access ATA TOSHIBA THNS128G 0203 PQ: 0 ANSI: 5
[ 3.826124] sd 0:0:0:0: [sda] 250069680 512-byte logical blocks: (128 GB/119 GiB)
[ 3.826227] sd 0:0:0:0: [sda] Write Protect is off
[ 3.826232] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 3.826278] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.827934] sda: sda1 sda2 sda3
[ 3.828454] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3.863366] device-mapper: uevent: version 1.0.3
[ 3.863509] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: [email protected]
[ 13.087453] random: nonblocking pool is initialized
[ 17.023466] NET: Registered protocol family 38
[ 17.304211] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 17.773165] thinkpad_ec: thinkpad_ec 0.41 loaded.
[ 17.776308] tp_smapi 0.41 loading...
[ 17.776557] tp_smapi successfully loaded (smapi_port=0xb2).
[ 17.785849] EXT4-fs (dm-0): re-mounted. Opts: data=ordered
[ 18.128026] Monitor-Mwait will be used to enter C-1 state
[ 18.128038] Monitor-Mwait will be used to enter C-2 state
[ 18.128045] Monitor-Mwait will be used to enter C-3 state
[ 18.128052] tsc: Marking TSC unstable due to TSC halts in idle
[ 18.128109] ACPI: acpi_idle registered with cpuidle
[ 18.128216] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
[ 18.128538] ACPI: Lid Switch [LID]
[ 18.128632] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3
[ 18.128638] ACPI: Sleep Button [SLPB]
[ 18.128774] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[ 18.128779] ACPI: Power Button [PWRF]
[ 18.133197] Switched to clocksource hpet
[ 18.157152] agpgart-intel 0000:00:00.0: Intel GM45 Chipset
[ 18.157193] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
[ 18.158391] agpgart-intel 0000:00:00.0: detected 32768K stolen memory
[ 18.158864] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[ 18.161295] thermal LNXTHERM:00: registered as thermal_zone0
[ 18.161300] ACPI: Thermal Zone [THM0] (49 C)
[ 18.163180] thermal LNXTHERM:01: registered as thermal_zone1
[ 18.163184] ACPI: Thermal Zone [THM1] (47 C)
[ 18.201123] systemd-journald[151]: Received request to flush runtime journal from PID 1
[ 18.211042] tpm_tis 00:05: 1.2 TPM (device-id 0x1020, rev-id 6)
[ 18.211049] tpm_tis 00:05: Intel iTPM workaround enabled
[ 18.214146] Non-volatile memory driver v1.3
[ 18.215056] ACPI: Battery Slot [BAT0] (battery present)
[ 18.216407] ACPI: AC Adapter [AC] (on-line)
[ 18.254681] [drm] Initialized drm 1.1.0 20060810
[ 18.486984] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 18.488981] ACPI Warning: SystemIO range 0x0000000000001028-0x000000000000102f conflicts with OpRegion 0x0000000000001000-0x000000000000107f (\_SB_.PCI0.LPC_.PMIO) (20140724/utaddress-258)
[ 18.488992] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 18.488998] ACPI Warning: SystemIO range 0x00000000000011b0-0x00000000000011bf conflicts with OpRegion 0x0000000000001180-0x00000000000011ff (\_SB_.PCI0.LPC_.LPIO) (20140724/utaddress-258)
[ 18.489003] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 18.489006] ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011af conflicts with OpRegion 0x0000000000001180-0x00000000000011ff (\_SB_.PCI0.LPC_.LPIO) (20140724/utaddress-258)
[ 18.489011] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 18.489014] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 18.489532] wmi: Mapper loaded
[ 18.496450] i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
[ 18.528954] thinkpad_acpi: ThinkPad ACPI Extras v0.25
[ 18.528960] thinkpad_acpi: http://ibm-acpi.sf.net/
[ 18.528962] thinkpad_acpi: ThinkPad BIOS 6EET55WW (3.15 ), EC 6EHT11WW-1.05
[ 18.528965] thinkpad_acpi: Lenovo ThinkPad X301, model 27763JG
[ 18.562827] mei_me 0000:00:03.0: irq 27 for MSI/MSI-X
[ 18.576844] thinkpad_acpi: detected a 16-level brightness capable ThinkPad
[ 18.578163] thinkpad_acpi: radio switch found; radios are enabled
[ 18.578329] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
[ 18.578333] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
[ 18.589581] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
[ 18.589742] thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
[ 18.593495] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input5
[ 18.602509] input: PC Speaker as /devices/platform/pcspkr/input/input6
[ 18.608125] cfg80211: Calling CRDA to update world regulatory domain
[ 18.608227] [drm] Memory usable by graphics device = 2048M
[ 18.608232] checking generic (d0000000 500000) vs hw (d0000000 10000000)
[ 18.608235] fb: switching to inteldrmfb from VESA VGA
[ 18.608267] Console: switching to colour dummy device 80x25
[ 18.608458] [drm] Replacing VGA console driver
[ 18.627881] Intel(R) Wireless WiFi driver for Linux, in-tree:
[ 18.627886] Copyright(c) 2003- 2014 Intel Corporation
[ 18.628049] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 18.628121] iwlwifi 0000:03:00.0: irq 28 for MSI/MSI-X
[ 18.633437] i915 0000:00:02.0: irq 29 for MSI/MSI-X
[ 18.633498] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 18.633501] [drm] Driver supports precise vblank timestamp query.
[ 18.633597] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 18.643232] iwlwifi 0000:03:00.0: loaded firmware version 8.83.5.1 build 33692 op_mode iwldvm
[ 18.691553] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 18.691558] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[ 18.691561] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[ 18.691565] iwlwifi 0000:03:00.0: Detected Intel(R) Ultimate N WiFi Link 5300 AGN, REV=0x24
[ 18.691646] iwlwifi 0000:03:00.0: L1 Disabled - LTR Disabled
[ 18.728972] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: data=ordered
[ 18.767043] iTCO_vendor_support: vendor-support=0
[ 18.775548] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 18.775618] iTCO_wdt: Found a ICH9M-E TCO device (Version=2, TCOBASE=0x1060)
[ 18.781996] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 18.792476] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 18.822944] iwlwifi 0000:03:00.0 wls1: renamed from wlan0
[ 18.836659] fbcon: inteldrmfb (fb0) is primary device
[ 19.343552] Console: switching to colour frame buffer device 180x56
[ 19.352308] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 19.352310] i915 0000:00:02.0: registered panic notifier
[ 19.375020] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
[ 19.397558] acpi device:01: registered as cooling_device2
[ 19.398077] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
[ 19.398394] [drm] Initialized i915 1.6.0 20140725 for 0000:00:02.0 on minor 0
[ 19.398598] snd_hda_intel 0000:00:1b.0: irq 30 for MSI/MSI-X
[ 19.444984] sound hdaudioC0D0: CX20561 (Hermosa): BIOS auto-probing.
[ 19.445424] sound hdaudioC0D0: autoconfig: line_outs=1 (0x1a/0x0/0x0/0x0/0x0) type:speaker
[ 19.445428] sound hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 19.445432] sound hdaudioC0D0: hp_outs=2 (0x19/0x16/0x0/0x0/0x0)
[ 19.445435] sound hdaudioC0D0: mono: mono_out=0x0
[ 19.445438] sound hdaudioC0D0: dig-out=0x1c/0x0
[ 19.445440] sound hdaudioC0D0: inputs:
[ 19.445444] sound hdaudioC0D0: Mic=0x18
[ 19.445447] sound hdaudioC0D0: Internal Mic=0x1d
[ 19.445450] sound hdaudioC0D0: Dock Mic=0x17
[ 19.446528] sound hdaudioC0D0: Enable sync_write for stable communication
[ 19.460104] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input9
[ 19.460484] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 19.460612] input: HDA Intel Dock Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 19.460739] input: HDA Intel Dock Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 19.460861] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
[ 19.507357] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1a0b1, caps: 0xd047b3/0xb40000/0xa0000, board id: 71, fw id: 572156
[ 19.507368] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0
[ 19.552922] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input7
[ 19.553788] iwlwifi 0000:03:00.0: L1 Disabled - LTR Disabled
[ 19.554188] iwlwifi 0000:03:00.0: Radio type=0x0-0x2-0x0
[ 19.559479] mousedev: PS/2 mouse device common for all mice
[ 19.687534] iwlwifi 0000:03:00.0: L1 Disabled - LTR Disabled
[ 19.687940] iwlwifi 0000:03:00.0: Radio type=0x0-0x2-0x0
[ 19.715231] IPv6: ADDRCONF(NETDEV_UP): wls1: link is not ready
[ 20.522949] cfg80211: Calling CRDA to update world regulatory domain
[ 23.184174] wls1: authenticate with 34:31:c4:5f:07:d1
[ 23.190197] wls1: send auth to 34:31:c4:5f:07:d1 (try 1/3)
[ 23.193077] wls1: authenticated
[ 23.193382] wls1: associate with 34:31:c4:5f:07:d1 (try 1/3)
[ 23.201867] wls1: RX AssocResp from 34:31:c4:5f:07:d1 (capab=0x431 status=0 aid=4)
[ 23.213427] wls1: associated
[ 23.213484] IPv6: ADDRCONF(NETDEV_CHANGE): wls1: link becomes ready
[ 23.213555] cfg80211: Calling CRDA to update world regulatory domain
[ 24.474590] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 24.727431] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input14
[ 26.135183] fuse init (API version 7.23)
[ 325.938870] wls1: AP 34:31:c4:5f:07:d1 changed bandwidth, new config is 2432 MHz, width 1 (2432/0 MHz)
[ 1198.431306] perf interrupt took too long (2511 > 2495), lowering kernel.perf_event_max_sample_rate to 50100
[ 1284.185106] tun: Universal TUN/TAP device driver, 1.6
[ 1284.185111] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
[ 1284.215129] Bridge firewalling registered
[ 1284.229704] device tap0 entered promiscuous mode
[ 1284.241864] IPv6: ADDRCONF(NETDEV_UP): qemubr0: link is not ready
[ 2126.210933] wls1: AP 34:31:c4:5f:07:d1 changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz)
[ 2426.034294] wls1: AP 34:31:c4:5f:07:d1 changed bandwidth, new config is 2432 MHz, width 1 (2432/0 MHz)
[ 2892.936374] kvm: zapping shadow pages for mmio generation wraparound
[ 2911.505834] kvm [958]: vcpu0 disabled perfctr wrmsr: 0xc1 data 0xffff
ip link / addr on host:
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wls1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:21:6a:a9:49:ae brd ff:ff:ff:ff:ff:ff
inet 192.168.178.32/24 brd 192.168.178.255 scope global wls1
valid_lft forever preferred_lft forever
inet6 fe80::2176:234a:73c6:16a7/64 scope link
valid_lft forever preferred_lft forever
3: tap0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop master qemubr0 state DOWN group default qlen 500
link/ether 7a:16:ef:9e:39:78 brd ff:ff:ff:ff:ff:ff
4: qemubr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 7a:16:ef:9e:39:78 brd ff:ff:ff:ff:ff:ff
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wls1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether 00:21:6a:a9:49:ae brd ff:ff:ff:ff:ff:ff
3: tap0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop master qemubr0 state DOWN mode DEFAULT group default qlen 500
link/ether 7a:16:ef:9e:39:78 brd ff:ff:ff:ff:ff:ff
4: qemubr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 7a:16:ef:9e:39:78 brd ff:ff:ff:ff:ff:ff
VM ip addr / link
http://oi58.tinypic.com/16kt11k.jpg
VM dmesg (extract), probably not helpful
http://oi59.tinypic.com/2i7l2qv.jpg
I must admit that my theoretical and practical knowledge on networking is quite limited, so this might be trivial. I'd be happy about any hints in the right direction. Thanks
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code and please don't post images of text [jwr] --
Last edited by AndyBrandi (2015-01-01 17:48:08)

You are scratching your right ear with the left hand, so to speak.
Let's say on the host, you have a bridge, br0, with an appropriate IP, serving as a gateway (created with your favorite network manager), and you'd like to start a VM whose virtual drive is arch-x86_64, then this is all you need to do:
$ qemu-system-x86_64 -enable-kvm -drive file=arch-x86_64,if=virtio -net nic,model=virtio -net bridge,br=br0
inside the VM you'll have eth0 (or whatever), and on the host -- tap0 plugged into the bridge. This is all courtesy of /usr/lib/qemu/qemu-bridge-helper which is a suid binary.
Last edited by Leonid.I (2015-01-03 23:24:41)

Solaris 10 cannot recognize tape device in library.

We have a DLT7000 tape device in a Quantum PX100 library connected to a Solaris 10 server via SCSI Adapter: X6541A. We can see the tape drive via OBP:
/pci@1e,600000/scsi@2
Target b
Unit 0 Removable Tape QUANTUM DLT7000 2565
But when Solaris 10 is loaded, there are no rmt links in the device tree. I've looked at devlinks and st.conf and made the changes I've read about online, but nothing seems to work. I've installed the following QLOGIC drivers, but they do not help. The only thing left is verifying jumpers? Terminators? But the question remains, if the system sees the tape drive at the OBP, then what's going on with the software? There's an sgen.conf file in /kernel/drv, but no sgscan type commands are available to use. I'm at a loss.
SUNWqus.tar.Z
SUNWqusu.tar.Z
SUNWqusx.tar.Z
SUNWqusux.tar.Z

Hello,
... connected to a Solaris 10 server via SCSI Adapter: X6541A. We can see the tape drive via OBP ...
... I've installed the following QLOGIC drivers, but they do not help.
Option X6541A is the Dual Differential Ultra/Wide SCSI (PCI) hba. The driver for this hba (based on SYM 53C876 chip) is already included with Solaris to support the integrated SCSI controller of most SPARC systems.
The QLogic drivers support Option X6758A PCI Dual Ultra3 SCSI Host Adapter (LVD).
But when Solaris 10 is loaded, there are no rmt links in the device tree
Rebuild the device tree either with boot -rv from the ok-prompt or devfsadm -c tape.
If you can afford the downtime, I would recommend the first choice.
Michael
Edited by: MAAL on 24.02.2010 06:45
Added information regarding the drivers for the hba.

I need a sdk and emulator for NEC mobile phones !!!

Can anyone have an idea where i can find this ?
thanks a lot

No, not that one either. I know Siemens has got some stuff, Nokia, Sony/Ericsson, Motorola (including their lovely GPS J2ME APIs) all have emulators, but the truth is I haven't seen any Asian (other than Sony) device vendor to provide emulator for their device. As I said, please go and talk to them directly - I guess they might have something.

[SOLVED] OpenVPN - tap device does not come up

I am trying to connect to an OpenVPN server. The server configuration is good; it works for Windows clients.
When I try to connect my Arch box, it says everything is good:
Aug 30 18:47:52 morpheus openvpn[7862]: Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Aug 30 18:47:52 morpheus openvpn[7862]: Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Aug 30 18:47:52 morpheus openvpn[7862]: Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Aug 30 18:47:52 morpheus openvpn[7862]: Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Aug 30 18:47:52 morpheus openvpn[7862]: Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
Aug 30 18:47:52 morpheus openvpn[7862]: [natoau] Peer Connection Initiated with 59.xxx.xxx.93:1115
Aug 30 18:47:54 morpheus openvpn[7862]: SENT CONTROL [natoau]: 'PUSH_REQUEST' (status=1)
Aug 30 18:47:54 morpheus openvpn[7862]: PUSH: Received control message: 'PUSH_REPLY,route 172.31.0.0 255.255.0.0 172.31.1.1,route-ipv6 2001:44b8:xxxxxx/56 2001:44b8:xxxxxxxxx::f0,route 192.168.0.0 255.255.254.0 172.31.1.1,ping 10,ping-restart 360'
Aug 30 18:47:54 morpheus openvpn[7862]: OPTIONS IMPORT: timers and/or timeouts modified
Aug 30 18:47:54 morpheus openvpn[7862]: OPTIONS IMPORT: route options modified
Aug 30 18:47:54 morpheus openvpn[7862]: ROUTE default_gateway=192.168.xxx.30
Aug 30 18:47:54 morpheus openvpn[7862]: TUN/TAP device tap0 opened
Aug 30 18:47:54 morpheus openvpn[7862]: TUN/TAP TX queue length set to 100
Aug 30 18:47:54 morpheus openvpn[7862]: /usr/sbin/ip route add 172.31.0.0/16 via 172.31.1.1
Aug 30 18:47:54 morpheus openvpn[7862]: ERROR: Linux route add command failed: external program exited with error status: 2
Aug 30 18:47:54 morpheus openvpn[7862]: /usr/sbin/ip route add 192.168.0.0/23 via 172.31.1.1
Aug 30 18:47:54 morpheus openvpn[7862]: ERROR: Linux route add command failed: external program exited with error status: 2
Aug 30 18:47:54 morpheus openvpn[7862]: Initialization Sequence Completed
The route errors are because the tap0 device doesn't actually come up; the "link" remains down, and no address is assigned:
# ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 6c:f0:49:e8:64:28 brd ff:ff:ff:ff:ff:ff
inet 192.168.x.x/27 brd 192.168.x.31 scope global eth0
inet6 2001:44b8:4121:xxxxxxxxxxxxxxxxx/64 scope global dynamic
valid_lft 86396sec preferred_lft 14396sec
inet6 fe80::6ef0:49ff:fee8:6428/64 scope link
valid_lft forever preferred_lft forever
Forcing the link up makes the device appear in the ip output, but still no address:
morpheus /etc/openvpn # ip link set tap0 up
morpheus /etc/openvpn # ip a s
11: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 100
link/ether 86:b9:40:dc:b6:da brd ff:ff:ff:ff:ff:ff
inet6 fe80::84b9:40ff:fedc:b6da/64 scope link
valid_lft forever preferred_lft forever
I've also tried a netcfg profile for the same config; same result.
Any ideas why tap0 doesn't want to come up?
Last edited by fukawi2 (2012-09-04 05:12:36)

FYI, I had to change my Windows config to up an --up script to explicitly request the DHCP address:
# this script brings the tap device up and starts a dhcpcd client on it
script-security 2
up /etc/openvpn/postup.sh
# we we wait until that's finished before adding routes...
route-delay 10
#!/bin/bash
tap_dev=$1
tap_mtu=$2
link_mtu=$3
ifconfig_local_ip=$4
ifconfig_netmask=$5
/usr/sbin/ip link set $tap_dev up
/usr/sbin/dhcpcd --background -L -t 10 --nogateway $tap_dev
exit 0
It's a bit (lot) of a hack, but it works. I have to start dhcpcd in the background otherwise OpenVPN seems to timeout the --up script and abort everything. I couldn't find how to extend the time limit that --up is allowed to run for.
This article helped point me in the right direction:
http://hans.fugal.net/blog/2009/01/06/p … its-place/

SCSI Emulation for IDE Tape Devices

Similar Messages

Maybe you are looking for