AT-GPIB/TNT board driver with linux kernel 2.2.16

I have installed AT-GPIB/TNT board to my linux computer. I downloaded the driver 0.5.1 from ni web site, installed with no problem.
First I used Window98 OS to test my hardware setup. My GPIB board is connect HP E3632A DC Power supply. I can use window version's ibic to run ibfind, ibdev, ibwrt, ibrd. Then I booted to linux, load the drive. But when I run ibwrt, give "EBUS" error. I used small test program to verify that I would get the same error. But I couldn't get it from Windows.
Where is my problem? inside the driver? or linux driver setup?
Thank you in advance
Allyson

Version 0.6 of the BETA driver is available at:
http://www.ni.com/linux
See if this new release gives you better performance
Ryan Mosley

Similar Messages

Instrument not recognized - computer too fast for AT-GPIB/TNT board

I have a problem with a potentiostat (PAR 283) connected to ISA AT-GPIB/TNT (not pnp) board. I recently upgraded to a motherboard with 1.8GHz AMD processor. Potentiostat is recognized by other software as "28PD", "28PE" or sometimes just some garbage characters, instead of "283". I'm using driver version 1.6 (1.7 could not recognize the board). In "Measurement&Automation" potentiostat doesn't respond to *IDN? query (error EAB0). FRA analyzer connected to the same board is recognized without a problem. None of the Windows programs can control potentiostat (it's not recognized as "283). One DOS program, however, is able to recognize and control the potentiostat. I tested the whole system with 166MHz compu
ter, and everything worked fine.
My operating system is Win98
Does anyone have idea what could solve the problem?
Thanks
Darko

I don't necessarily have an answer to your problem, but I want to assure you those usually these problems are with the instrument. The IEEE 488.1 standard defines a 3-wire interlocked handshake to prevent any problems due to computer/device speeds.
However, some devices violate this protocol. They rely on internal timing to determine when things should occur on the bus. For example, the talker asserts the DAV hardware line to indicate that data is valid on the bus. Following that, the listener is supposed to latch the data from the bus and then assert NDAC to indicate that it has taken the data from the bus. At the moment that NDAC has been asserted, the talker is allowed to modify the data lines since they have already been latched. However, some devices have noted in the past that their is usually X amount of time that passes from when NDAC is asserted until the data is removed from the wire. In order to improve peformance, they actually assert NDAC sometime before the data has been latched, assuming that the data will be there when they are actually ready to receive this data. In the case of moving to a faster computer, this data is actually staying on the bus for a shorter period of time than expected and the device receives garbage data.
A similar phenomenon can occur when the device is the talker where is violates the proper 3-wire handshake.
Note that not all failures are intential on the side of the device, it could be a legitimate bug.
Now that I have given a somewhat long-winded description of how problems like this can manifest, I can give you a few recommendations.
1) Obtain a GPIB bus analyzer and examine the handshake sequence to determine where the failure is.
2) Talk to the equipment manufacturer to see if they have any updates
3) Modify the bus timing in NI-488.2 from 500ns to 2ms. This is not likely to work since you are on the receiving end.
4) Try to procure a GPIB-PCII/IIA board. This is a slower board that overall responds to handshaking slower than the AT-GPIB/TNT board and may mask the problem.
5) Increase your cable length (including to "illegal" lengths such as 8m). This can add propegation delays that can mask this problem. I have seen work in teh past with troubled instruments.
Good luck.

Dual channel receiver works with NI-PC2/driver v2.6 but not NI-GPIB/TNT(PNP)/driver v2.7.2

I posted a message earlier but didn't word it correctly. We have a Microdyne 2800 receiver that we would like to set up remotely via 488. The receiver works fine in DOS using an older NI-PC2 card with the v2.6 drivers that came with it. However, when we switch to the newer PC-GPIB/TNT(PNP) 488 card with the latest DOS drivers, v2.7.2, it doesn't respond. The receiver recognizes that it received something via the bus but does nothing (it has a little red light that turns on when in remote mode). What prompted us to test it in DOS was that the same thing was happening under WinNT 4.0 using the PNP card and the v1.60 drivers.
In ibic, I'm using the exact same
sequence of commands to setup the card (ibdev, ibclr, and then ibln) and then I use the ibwrt to write the setup string to it. Are there any differences in the cards and/or drivers that I should be aware of?
Thanks for any help!

Dear Sr.,
This kind of troubleshooting can be extensive so I recommend you to call us in Technical Support to address your issue, you can find the information at:
http://sine.ni.com/apps/we/niae_asc.main
Some of the common questions I'd ask you about this will be:
1. Has this board work before?
2. Have you tried it in another computer?
3. When installing the board, did you ran the configuration utility and did the query and scan for instruments? (Start > Programs > National Instruments > NI-488.2 > Explore GPIB.... click F5 to Refresh then Select your board from "Devices and Interfaces" and click "Scan for Instruments" then when it finds your instrument click "Communicate with Instrument" and then click "Query")
4. Have you tried this IBIC procedure? http://www.ni.com/su
pport/gpib/max/ibic.htm
5. Take a look at this link, it may be of help: http://www.ni.com/support/gpib/dos/attntpnp/default.htm
6. What type of termination character does your instrument uses?
If after looking at this questions and links your board still is not working please give us a call, we may need to try different workarounds or need more information from your system. As far as the information you wrote your board should work fine. Also, I can assume from your info that you have a 488.2 compatible instrument, is this correct?
Regards,
Nestor Sanchez
Applications Engineering
National Instruments
Nestor
National Instruments

How to program VC++ with AT-GPIB-TNT

I am a student in Taiwan and a beginner user in GPIB.
I am writing a control program in Visual C++(console) on Win98 (by N.I. GPIB-TNT
board).
I need to control two devices one is Laser interferometer for measurement,
another is PZT(piezo actuator).
When I execute a simple read and write program,
it always shows " can not read ".
I am so confused.
Can you help me to overcome this problem
and show me a new simple program?!
Thank you very much.....
I am so appreciate for your help.
best regards
Andrew

Andrew,
From the bottom of http://www.ni.com/support/trouble/gpib/max/ibic.htm, there is
a link to "Solutions to Common Errors." If you follow that link, the next page will
have an entry for the EABO error code (and several other error codes). These tips
are the suggestions that our support staff would make to you if you were to speak
with them. I suggest checking that link out. I have posted this message to the
newsgroup for the benefit of all readers.
Regards,
Rich
NI
Thanks for your help.
After receiving your mail, I try to follow the step.
But when I use "ibrd", it has the error code as follow
iberr = EABO
EABO indicates that an I/O operation has been canceled, usually due to a
timeout condition after a GPIB read.
Before reading from the instrument, verify that the GPIB command you are
sending is understood by your device
and instructs it to place data in its output buffer.
device data as follow
Board: GPIB0 AT-GPIB/TNT
Device: Name Type
Value Description
instrument0 Instrument is not 488.2 compatible pad=2 GPIB
instrument
instrument1 Zygo, VMEbus control board pad=3 GPIB
instrument
My goal just want to read the measuring data from laser device by
AT-GBIP/TNT board.
Need your help again thanks.
Andrew
> Andrew,
>
> What you may want to do, instead of starting off with straight
coding, is
> to see if you can establish communication with the instrument using
"IBIC," our
> interactive diagnostic tool for instrument control. This program comes
> installed with your 488.2 driver.
>
> To find out more about this, visit
> http://www.ni.com/support/trouble/gpib/max/ibic.htm . If you can achieve
> communication with your instruments with this program, you're well on your
way.
> If you cannot, the website has solutions to common errors that one can see
while
> using this tool.
> ps. "threads" refer to the number of processes running at once. For
example,
> if you can do two separate math operations simultaneously in your program,
> that's a multithreaded application.
> "andrew" on 04/24/2000 03:51:13 AM
> I am a student in Taiwan and a beginner user in GPIB.
> I got your e-mail address from your post on N.I. user newsgroups.
> I am writing a control program in Visual C++(console) on Win98 (by N.I.
GPIB-TNT
> board).
> I need to control two devices one is Laser interferometer for measurement,
> another is PZT(piezo actuator).
> When I execute a simple read and write program,
> it always shows " can not read ".
> I am so confused.
> Can you help me to overcome this problem?
> And show me a new simple program!
> Thank you very much.....
>
> I am so appreciate for your help.
>
> best regards
> Andrew
>
> Ps.what is singlethreaded and multithreaded?

Bluescreen on Win NT with AT/GPIB TNT!

I have a AT/GPIB TNT board and 488.2 version 1.60 software. The computer crashes randomly and the "blue screen" on NT always appears, with this line included: IRQL_NOT_LESS_OR_EQUAL ** -gpibclsd.sys
and sometimes
IRQL_NOT_LESS_OR_EQUAL ** -afd.sys
I´ve tried several things but none work except for when I run it without network connection.
Anyone have a good answer??
/Sohrab, Ericsson Microwave Systems

I have heard of this before but haven't been able to reproduce the error. If it works without a network connection/ you might want to try a different network interface card.
Just so you have the latest updates...
there's a patch for LabWindows/CVI 5.5, http://digital.ni.com/softlib.nsf/websearch/090082BECD7AC973862568EA005704EE?OpenDocument&node=132070_US
The latest VISA version, 2.6 can be downloaded from, ni.com > Support > Product Reference > Drivers and Updates > Current Versions, and for the latest Instrument Drivers refer, http://zone.ni.com/idnet97.nsf/browse/

PCI-GPIB card not found in linux 2.4.22-1.2115.nptl Fedora Core 1

I am trying to install the nigpib driver on a Fedora Core 1 installation of linux (kernel 2.4.22-1.2115.nptl.) The installation script reports the following errors:
Your kernel appears to be configured properly to build NI-GPIB for Linux.
Do you want to proceed? [yn] y
make: `nigpib.o' is up to date.
Copied nigpib.o driver to modules directory /lib/modules/2.4.22-1.2115.nptl/kernel/drivers/char
Devices created.
Probing for PCI-GPIB.
No PCI-GPIB boards detected.
Do you have an AT-GPIB/TNT board installed? [ny] n
/etc/modules.conf is up to date.
Warning: loading /lib/modules/2.4.22-1.2115.nptl/kernel/drivers/char/nigpib.o will taint the kernel: no license
See http://www.tux.org/lkm
l/#export-tainted for information about tainted modules
/lib/modules/2.4.22-1.2115.nptl/kernel/drivers/char/nigpib.o: init_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-1.2115.nptl/kernel/drivers/char/nigpib.o: insmod /lib/modules/2.4.22-1.2115.nptl/kernel/drivers/char/nigpib.o failed
I have moved the PCI-GPIB card to the first PCI slot with no differences in the error messages I recieve. When I run dmesg I recieve the following information:
unable to get major 31 for gpib
unable to get major 31 for gpib
unable to get major 31 for gpib
unable to get major 31 for gpib
unable to get major 31 for gpib
Any help would be appreciated.

I have this same exact problem. I'd rather not disable USB 2.0, because I use it to transfer files to my MP3 player when in Windows.
I find it hard to "blame the BIOS" when it was working fine under kernel 2.6.7. Anyone know of another solution?
EDIT: Well it isn't the same "exact" problem. When I first boot into Arch, the usb mouse and keyboard don't work. I press and hold the power button on the machine to restart. The second time I boot into Arch, the usb devices do work. If I do a standard soft reboot and go back into Arch, the usb devices again don't work. I guess this is a hotplugging issue, but enabling it in rc.conf does nothing. The only permanent solution I can find is disabling USB 2.0 in the BIOS.

What format structure do I reformat the hard drive with?

I'm reformatting my hard drive with linux and need to know which structure i use to format it with. the choices are:
FAT
ext2
ext3
ext4 reiserfs
minix
ntfs
nilfs2
Swap Space
Empty
Don't want to guess at his point and get it wrong. Thanks for you help
whereisjeff

What are you formatting the disk to do?
If it is to work with a Mac, you want HFS+ (Journaled) with GUID partition mapping.
Allan

Nigpib-linux-0.6 GPIB software driver for Linux and PXI GPIB board

My I use nigpib-linux-0.6 GPIB software driver for Linux in a Compact PCI system running linux and equipped with your PXI GPIB board ?
Thanks.
Paolo Santinelli.
[email protected]

If you alter the device ID of the device from c801 to c821 within the driver module, you should be able to use the driver with the PXI board.

CentOS based linux VM running on Hyper-v : Checking root filesystem fails when kernel switches having old PV(para virtualised driver based on 2.6.32 linux kernel) to new PV(which is equivalent to linux integration component 3.4)

hi all,
I am running a CentOS base VM on top of Hyper-V server. I upgraded PV drivers of Hyper-V in linux kernel 2.6.32 in order to support
Windows Server 2012, then i am hitting below issue on Windows Server 2008 when kernel switches from old PV(which is 2.6.32 based) to new PV(which is equivalent to linux integration component 3.4).i
am hitting following filesystem check error messages :
Setting hostname hostname:
Checking root filesystem
fsck.ext3/dev/hda2:
The superblock could not be read or does not describe correct ext2 filesystem. If the device is valid and it really contains an ext2
filesystem(and not swap or ufs or something else),then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
: No such file or directory while trying to open /dev/hda2
*** An error occurred during the filesystem check.
*** Dropping you to a shell; the system will reboot
*** When you leave the shell.
Also, when I go to the repair filesystem mode. I found out the strange behaviour when i ran those command :
(Repair filesytem) 1 # mount
/dev/hda2 on / type ext3 (rw)
proc on /proc type proc (rw)
(Repair filesystem) 1# cat /etc/mtab
/dev/hda2 /ext3 rw 0 0
proc /proc proc rw 0 0
(Repair filesystem) 1# df
Filesystem 1K-blocks used Available Use% Mountedon
/dev/hda2 4%
I think for all above command there should be /dev/sda2 instead of /dev/hda2.
Also my fstab , and fdisk -l looks like ok for me.
(Repair filesystem) 1# cat /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
LABEL=swap-xvda3 swap swap defults 0 0
(Repair filesystem) 1# fdisk -l
Device Boot Start End Block Id System
/dev/sda1 * 1 49 98535 83 Linux
Partition 1 does not end with cylinder boundary.
/dev/sda2 49 19197 39062500 83 Linux
Partition 2 does not end with cylinder boundary.
/dev/sda3 ......
Partition 3 does not ......
/dev/sda4 ......
Partition 4 does not end ....
(Repair filesystem) 1# e2label /dev/sda1
/boot
(Repair filesystem) 1# e2label /dev/sda2
(Repair fielsystem) 1# ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4
(Repair filesyatem) 1# ls /dev/hd*
ls: /dev/hd*: No such file or directory
Kindly suggest any configuration of windows server or kernel configs missing or how to resolve this issues
Many many thanks for your reply.
thanks & Regards,
Ujjwal

i am not able to understand duplicate UUID and from where it is picking /dev/hda* ?
~
VVM:>>
VVM:>> Output of dmesg | grep ata contain substring "Hyper-V" ?
VVM:>>
it doesn't contain "Hyper-V" or ata related message and the output doesn't change with boot parameter reserve=0x1f0, 0x8
~~
~~~~
==
output of dmesg related "ata" Ubuntu v13.04 mini.iso ( with boot parameter reserve=0x1f0, 0x8)
==
see later ( in "good situation" example )
~~
===
Disable legacy ATA driver by adding the following to kernel command line in /boot/grub/menu.lst:
reserve=0x1f0, 0x8
. (This option reserves this I/O region and prevents ata_piix from loading).
==
See output of dmesg related "ata" Ubuntu v13.04 mini.iso ( with boot parameter reserve=0x1f0, 0x8) :
~~
[ 0.176027]
libata version 3.00 loaded.
[ 0.713319]
ata_piix 0000:00:07.1: version 2.13
[ 0.713397]
ata_piix 0000:00:07.1: device not available (can't reserve [io 0x0000-0x0007])
[ 0.713404]
ata_piix: probe of 0000:00:07.1 failed with error -22
[ 0.713474]
pata_acpi 0000:00:07.1: device not available (can't reserve [io 0x0000-0x0007])
[ 0.713479]
pata_acpi: probe of 0000:00:07.1 failed with error -22
~~
As result: 1) IDE disk handled by hv_storvsc , but 2) no CD-ROM device
==
~ # blkid
/dev/sda1: LABEL="ARCH_BOOT" UUID="009c2043-4bl7-4f95-al4d-fb8951f95b5d" TYPE="ext2"
==
~~
VVM>>
VVM>>Q1: Output of blkid contain duplicate UUID ?
VVM>>
-> blkid contains duplicate UUID, below are the output.
~~
This situation is classic problem "
use hv_storvsc instead of ata_piix to handle the IDE disks devices ( but not for the DVD-ROM / CD-ROM device handling)
~~
For compare, see example "good situation":
See output of dmesg related "ata" Ubuntu v13.04 mini.iso ( without boot parameter reserve=0x1f0, 0x8) :
~~~~
~ # dmesg |grep ata
[ 0.167224] libata version 3.00 loaded.
[ 0.703109] ata_piix 0000:00:07.1: version 2.13
[ 0.703267] ata_piix 0000:00:07.1: Hyper-V Virtual Machine detected, ATA device ignore set
[ 0.703339] ata_piix 0000:00:07.1: setting latency timer to 64
[ 0.704968] scsi0 : ata_piix
[ 0.705713] scsi1 : ata_piix
[ 0.706191] atal: PATA max UDMA/33 cmd 0xlf0 ctl 0x3f6 bmdma 0xffa0 irq 14
[ 0.706194] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
[ 0.868844] atal.00: host indicates ignore ATA devices, ignored
[ 0.869142] ata2.00: ATAPI: Virtual CD, , max MWDMA2
[ 0.871736] ata2.00: configured for MWDMA2
~~~~
===
~ # uname -a
Linux ubuntu 3.7.0-7-generic #15-Ubuntu SUP Sat Dec 15 14:13:08 UTC 2012 x86_64 GNU/Linux
~ # lsmod
hv_netvsc 22769 0
hv_storvsc 17496 3
hv_utils 13569 0
hv_vmbus 34432 3 hv_netvsc,hv_storvsc,hv_utils
~ # blkid
/dev/sr0: LABEL=”CDROM" TYPE="iso9660”
/dev/sda1: LABEL="ARCH_BOOT" UUID="009c2043-4bl7-4f95-al4d-fb8951f95b5d" TYPE="ext2"
===
( only CD-ROM and 1( one) IDE disk connected to ATA)
~~
regarding ata_piix.c patch . . .
As far as i understand this patch , it ignore ATA devices on Hyper-V when PV drivers(CONFIG_HYPERV_STORAGE=y) are enabled.
~~
Yes:
ignore ATA-HDD ( but not ignore ATA CD-ROM ) on Hyper-V when PV drivers(CONFIG_HYPERV_STORAGE=y) are enabled.
~
this patches need be backported:
cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default
and its prerequisite
db63a4c8115a libata: add a host flag to ignore detected ATA devices
~
~~
P.S.
Are You do this:
==
As temporary solution, increase on 1-2 Gb size all .vhd connected to IDE bus
( but not increase size of partitions inside disks)
==
? fsck write message a-la: "no error in file system" ?
2013-01-24 Answer by Ujjwal Kumar: As a temporary solution looks ok for me, but [ VVM: need true solution ]
P.P.S.
To Ujjwal Kumar :
My e-mail:
ZZZZZZZZZZZZZZZ
please send e-mail to me, in reply I send to You patches to ata_piix ( and *.c before and after patches) , etc.
} on 2013-01-14 -- DoNe

I need the linux (kernel 2.2)drivers for my NI-DAQ lpm 16

I'm doing a proyect with your NI-DAQ lpm 16 and i need a driver for use with linux red hat 6.0 that have kernel 2.2 .
I can't find this driver in your page and i need it urgently.
Many thanks and i'm sorry for my english.

Hello,
You posted your question to the "Measure" forum, which is for questions pertaining to the National Instruments product "Measure for Windows". In order to get the best possible audience for your particular question, I recommend you post to the "Multifunction I/O" discussion forum.
Good luck, and have a pleasant day.
Darren
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

NI PMC-GPIB on Linux kernel version 3.11.10 (Fedora 20)

Can the NI PMC-GPIB run on Linux kernel version 3.11.10 (Fedora 20)?
The linux OS is a hard requirement.
Thanks

Hey Terry_ALE,
This card uses NI 488.2, and there are several supported versions of Linux, but Fedora 20 isn't one of them. That being said, I found another forum post where some users were able to get it to work.
The list of compatible Linux versions can be found here, and the forum with the workaround for Fedora can be found here.
I've also got to throw in the standard disclaimer with this advice: This is not a supported use case and any issues that arise from this configuration would be unsupported.
Hope this helps, and good luck iwth your application!
Tanner B.
Applications Engineer
National Instruments

Oracle 11.2.0.2g driver with IBM JRE(J2RE 1.5.0 IBM J9 2.3 Linux x86-32)

Hi All,
I am trying to use oracle 11.2 jdbc thin driver with IBM JRE and getting following exception messages.
Details from Ojdbc5.jar
Implementation-Version: 11.2.0.2.0
Repository-Id: JAVAVM_11.2.0.2.0_LINUX_100812.1
And Details from Java System Properties
java.vm.info: J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20060504 (JIT enabled)
J9VM - 20060501_06428_lHdSMR
JIT - 20060428_1800_r8
GC - 20060501_AA
java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:195)
at javax.crypto.Cipher.getInstance(Unknown Source)
at oracle.security.o5logon.O5LoginClientHelper.decryptAES(Unknown Source)
at oracle.security.o5logon.O5LoginClientHelper.generateOAuthResponse(Unknown Source)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:655)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:366)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:536)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:228)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1247)
at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1221)
at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111)
at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77)
at com.tes.archival.extractor.DataExtractorWithJdbcImpl.extractArchivalRecords(DataExtractorWithJdbcImpl.java:61)
at com.tes.archival.executor.ExtractorExecutor$1.call(ExtractorExecutor.java:57)
at com.tes.archival.executor.ExtractorExecutor$1.call(ExtractorExecutor.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:284)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:797)
Caused by: java.lang.SecurityException: Cannot set up certs for trusted CAs
at javax.crypto.b.<clinit>(Unknown Source)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
... 24 more
Caused by: java.lang.SecurityException: Jurisdiction policy files are not signed by trusted signers!
at javax.crypto.b.a(Unknown Source)
at javax.crypto.b.a(Unknown Source)
at javax.crypto.b.access$600(Unknown Source)
at javax.crypto.b$0.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:241)
... 27 more
Any help in resolving this issue will be much appreaciated.
Regards,
Raman

804915 wrote:
Caused by: java.lang.SecurityException: Cannot set up certs for trusted CAs
Caused by: java.lang.SecurityException: Jurisdiction policy files are not signed by trusted signers!Probably a permissions problem. Or something is wrong with the certs.

Partition an Advanced Format drive with 4KB sector (for Linux OS only)

I got a brand new WD 1TB drive, model WD10EZEX, I'm upgrading from an old 500 GB drive with Arch running on it, and I'm going to make a fresh Arch install on it.
I suddenly learned about all this Advanced Format issue, with the first units "lying" about physical sector size and all that stuff, which started like 2 years ago and I was not aware of.
I couldn't find a step by step guide to perform the proper formatting for a fresh Linux OS install with 4KB-sector, despite the info is out there scattered in tons of blogs, forums, etc.
I figured out the steps for my simple setup, and I'd like to know if everything is all right. For the ones who already know the steps, can you please go to the bottom of the post, and tell me if the final setup is all right to start the fresh install ?? I reproduce all the steps hoping that this will help other people in the future.
I'll use the whole drive only for an Archlinux install, with one partition for the / and another for /home.
Seems the GPT modern method is the way to go, and the gdisk tool will do the trick. If we are booting from this drive, with GRUB2 in a BIOS system, we must also create a BIOS Boot Partition.
So, with the drive having no partitions at all, and sda being the device name
# gdisk /dev/sda
Command (? for help): p
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 6527769B-B4BC-408C-A45B-D2DAA4036620
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 1953525101 sectors (931.5 GiB)
Number Start (sector) End (sector) Size Code Name
we create the 2 MiB BIOS Boot Partition
Command (? for help): n
Partition number (1-128, default 1): 1
First sector (34-1953525134, default = 2048) or {+-}size{KMGTP}: 2048
Last sector (2048-1953525134, default = 1953525134) or {+-}size{KMGTP}: +2M
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): ef02
a 45GB partition to use as /
Command (? for help): n
Partition number (2-128, default 2):
First sector (34-1953525134, default = 6144) or {+-}size{KMGTP}:
Last sector (6144-1953525134, default = 1953525134) or {+-}size{KMGTP}: +45G
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): 8300
Changed type of partition to 'Linux filesystem'
and the rest to use as /home
Command (? for help): n
Partition number (3-128, default 3): 3
First sector (34-1953525134, default = 94377984) or {+-}size{KMGTP}:
Last sector (94377984-1953525134, default = 1953525134) or {+-}size{KMGTP}:
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): 8300
Changed type of partition to 'Linux filesystem'
we can check the setup
Command (? for help): p
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 6527769B-B4BC-408C-A45B-D2DAA4036620
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 6143 2.0 MiB EF02 BIOS boot partition
2 6144 94377983 45.0 GiB 8300 Linux filesystem
3 94377984 1953525134 886.5 GiB 8300 Linux filesystem
and everything looks fine, we have the multiples of 8 starting sectors, so we write the changes
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sda.
The operation has completed successfully.
now we need to give the / and /home partitions a format, I choose ext4 and ask for a 4096 block size just in case we have a "lying" unit (not my case but I prefer to write down the most general command)
# mkfs.ext4 -b 4096 /dev/sda2
mke2fs 1.42.6 (21-Sep-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
2949120 inodes, 11796480 blocks
589824 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
360 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
and the same thing for /dev/sda3 .
Check with gdisk and parted that everything is fine, is this all right to start the install ??
# gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 6527769B-B4BC-408C-A45B-D2DAA4036620
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 6143 2.0 MiB EF02 BIOS boot partition
2 6144 94377983 45.0 GiB 8300 Linux filesystem
3 94377984 1953525134 886.5 GiB 8300 Linux filesystem
# parted /dev/sda
GNU Parted 3.1
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: ATA WDC WD10EZEX-00R (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 3146kB 2097kB BIOS boot partition bios_grub
2 3146kB 48.3GB 48.3GB ext4 Linux filesystem
3 48.3GB 1000GB 952GB ext4 Linux filesystem
Last edited by karamaz0v (2012-12-06 06:39:45)

Your partitions look fine from an Advanced Format point of view. The test is simple: Are all your partitions' start points, as measured in sectors, divisible by 8? Yours are.
karamaz0v wrote:what confused me a bit, was that I saw a lot of setups with the BIOS boot partition, and also a 200 MB EFI one. Having a BIOS system, I think I don't need the EFI one.
Some people do this because they're unclear of their requirements. Others do it because they want to have the option of switching boot modes between BIOS/legacy and EFI. With both types of boot loader installed, you can choose on a boot-by-boot basis which way to start the computer, assuming it supports both boot modes.

T400s Linux/Windows dual boot with Linux from Esata Flash Drive

This project is about a dual boot Windows/Linux system without using the normal dual boot changes in the bootloader of the windows hard drive. When I started this I found bits and pieces of information on the web but no complete description so I wrote this post.
I have done a dual boot system on my previous Thinkpad where I had partitioned the hard drive between Linux and windows. For this project I wanted to leave the windows hard drive absolutely intact and unaltered, and boot Linux from a flash drive in the esata port on the back of the T400s. Obviously this uses the F12 boot list function key to boot from the flash. The advantage of this is that Windows is totally unaltered and when I need Linux, I plug in the esata flash drive, hit F12 during the boot cycle and select booting from the esata flash drive. The reason for Esata rather than USB is simply speed. I have a nice fast Linux installation.
I used the OCZ esata flash drive but suspect any of the alternatives will work. It did not need the accessory usb cable because the Thinkpad powered the esata flash directly.
To boot from the esata drive I had to make the following changes in the bios
    I left the esata flash plugged in as I went into the bios
    Bios>config>Serial ATA and changed the Sata controller mode option to compatibility
    Restart and back into the Bios
    Bios>startup>boot - in my case the esata flash drive showed up as ATA HDD2 and was excluded from the boot order so I had to un-exclude it and move it to the point in the boot order that I wanted.
Next I downloaded a linux installation iso and put it on a CD - in my case opensuse. Then booted from the CD
From now on this instructions are specific to opensuse and yast but can be generalized to whatever Linux is being used.
In my case yast came up with a good set of suggestions for automatically partitioning the flash drive but then crashed during the partitioning itself. So I rebooted and specified the partitions manually.
    A fat32 partition left as a partition which both windows and Linux could see (in my case about 20% of the drive) (/dev/sdb1)
    An extended partition with the remainder of the drive (/dev/sdb2) which contains the following logical partitions
    A linux Swap partition of 2GB (/dev/sdb5)
    A linux /home partition –the remainder of the drive (/dev/sdb6)
    A linux /root partition of 8GB (/dev/sdb7)
Yast automatically suggested mount points of C,D,E for the windows partitions. Unfortunately because of the way the Thinkpad hard drive was laid out Yast had C assigned the ThinkPad Service partition and D assigned to the SW_Preload (or main windows partition). However there was an edit function that allows for the reversal of those mount points so that the windows C drive is mounted in Linux as Windows/C thereby avoiding confusion. I had already backed up and removed the Thinkpad factory install data so I did not have to deal with that. Yast suggested Windows/E for the mount point of the FAT32 partition on the flash drive, which I accepted.
The yast install configurator made all this manual selection easy, and after the manual configuration the partitioning worked perfectly.
Next step was Linux user configuration which went fine
Next was booting.
In the section management tab
    delete the windows 1 and 2 options (since we are not dual booting directly)
In the boot loader installation tab
    uncheck boot from mbr ( this stops the install from installing Grub and dual boot on the windows c drive
    check boot from root partition (this installs grub and all associated files in the Linux root partition (/dev/sdb6)
I believe that the correct procedure at this point is to click Boot Loader installation details which will bring up the Grub device map. In the device map there will be a line for the fixed hard drive (aka the windows drive) and a line for the esata flash drive. When the installer started up these were in hard drive and esata drive order. However when we boot directly from the flash the esata drive will be grub drive hd0 and the fixed hard drive will be grub hd1. The device map order needs to be changed to reflect this ie the esata drive should be first not second.
I did not do this and ended up initially doing Grub command line editing to boot and later manually editing the grub files using information I had previously learned the hard way and through google.
At this point let the installer go ahead and install Linux. After doing this it should come back and tell you to reboot. Do not do it yet because we need to install the MBR into the flash drive.
I suspect that there is a way of doing this in Yast running from the Live CD but it was not obvious to me so I used the manual method that I have used before.
Open a root terminal
Mount /dev/sdb6 to /mnt/sdb6 (my linux root)
Touch /mnt/sdb6/boot/grub/flag
The purpose of this is when we go looking later at the grub command prompt we need an easy to find unique file
Start grub and do the following
#grub
            grub> find /boot/grub/flag
                (hd1,5)    -- the result of the find in my example
            grub> root (hd1,5)   -- using the result of the find in my example
            grub> setup (hd1)   -- install mbr -- my example parameters - if you get this wrong you will trash some other drive!!!
                  hopefully grub announces success
            grub> quit
Reboot and select the flash drive. In my case I still had the grub devicemap wrong and had to edit the grub commands during boot to tell grub how to find the correct partition and then edit them again after booting
Typical linux install issues that we all always seem to have and can be solved with a little (or a lot of) google research.
As I said at the beginning I now have an untouched windows installation and a nice fast Linux installation. I hope that this will be of some use to someone.

Hi chrissh
i tried this exact procedure... on the exact same notebook (T400s). However, as soon as I set the
   Bios>config>Serial ATA to "compatibility", I cannot use my default Windows installation! I immediately get the "blue screen of death".
I doubt I did anything differently since this is the first step of your procedure and my laptop is brand new!
any idea?

Replace Linux with Hurd kernel

Hi
Can i Replace Linux with Hurd kernel?

Lone_Wolf wrote:
hayderctee,
there is an Archlinux Hurd project, http://www.archhurd.org/ but i have no idea how usable it is.
I would say that's dead, with no updates to any packages since March last year...

AT-GPIB/TNT board driver with linux kernel 2.2.16

Similar Messages

Maybe you are looking for