Sponsored Content
Full Discussion: Memory conflicts
Top Forums UNIX for Advanced & Expert Users Memory conflicts Post 11426 by ghoti on Wednesday 5th of December 2001 09:34:41 AM
Old 12-05-2001
Memory conflicts

Hi,

I am upgrading a Dell Inspiron 4000 from 128Mb to 512Mb, but if I put over 256Mb RAM into the machine, it is then unable to access the network card and modem (both PCMCIA).

I have seen something about Linux not being able to handle large amounts of physical RAM, but is there a way round this?

redhat 7.1 is currently installed, and there are a lot of sofware set up on this computer, so I would like to be able to reconfigure rather than reinstall.

Thanks,
-gHoTi
 

8 More Discussions You Might Find Interesting

1. Solaris

Software Dependencies Conflicts

Question: What do you do when you have a software dependency conflict? Case in point, according to Freeware for Solaris, before one can install tcl, tk must be installed first. And then when I go to investigate dependencies for tk, it says that tcl must be installed first!!! Its like... (2 Replies)
Discussion started by: RobSand
2 Replies

2. UNIX for Advanced & Expert Users

Virtual Hosts and Alteon DNS conflicts

Hi, This is more of a verification rather than a question of technical nature. This is based on solaris 10 machine Could we use Virtual hosts (within our hosts file): 123.1.1.10 virtual_host_name 123.1.1.10 host_A (note: 123.1.1.10 - host_A is also in our DNS server entry) And... (0 Replies)
Discussion started by: jackola
0 Replies

3. AIX

How do we fix the library conflicts?

How do we fix library conflicts? When I do ldd on Mysql Driver, I get an error ldd libmyodbc5.so libmyodbc5.so needs: /usr/lib/libdl.a(shr_64.o) Cannot find libodbcinst.so /usr/lib/libc.a(shr_64.o) /usr/lib/libpthreads.a(shr_xpg5_64.o) /unix ... (1 Reply)
Discussion started by: Hangman2
1 Replies

4. UNIX for Advanced & Expert Users

How do we resolve the library conflicts?

How do we resolve the library conflicts? ldd libmyodbc5.so libmyodbc5.so needs: /usr/lib/libdl.a(shr_64.o) Cannot find libodbcinst.so /usr/lib/libc.a(shr_64.o) /usr/lib/libpthreads.a(shr_xpg5_64.o) /unix /usr/lib/libcrypt.a(shr_64.o) (2 Replies)
Discussion started by: Hangman2
2 Replies

5. IP Networking

dhcp and static ip conflicts.

I have a USB Wireless Adapter using the rum0 driver. All I want to do is set a perminent static IP for the onboard wired interface elxl0. I can plumb the wired interface up fine on the fly, but when I try to save the static IP over a reboot, I lose the IP address assigned to rum0 from my wireless... (1 Reply)
Discussion started by: ts97783
1 Replies

6. UNIX and Linux Applications

mysql conflicts problem

:confused: hi all, RHEL 4 has installed on the server, when i use rpm -i command to install mysql5.1 enterprise version, error failed dependencies occurs as below: mysql conflicts with mysql-4.1.22-2.el4.i386 mysql conflicts with mysql-4.1.22-2.el4.x86_64 have tried rpm -e which was... (2 Replies)
Discussion started by: maxlee24
2 Replies

7. UNIX for Advanced & Expert Users

Conflicts in the output of TOP command

Hi All, In the output of TOP command in my unix system, i monitored that some process has utilization more than 100% even some process has 4000% utilisation. Please help me understand how it is possible to show more than 100% utilization. Please see the screenshot below:... (2 Replies)
Discussion started by: anand2308
2 Replies

8. Solaris

How to install SFE ips binaries? Conflicts.

I am trying to install binaries from the SFE repo with IPS package manager which I have added from: http://sfe.opencsw.org/localhosts11/ When I try to install some stuff, like VLC v2.1.5 or Wine v1.7.6, there are lot of conflicts. How to resolve them? I suspect SFE wants to install some... (0 Replies)
Discussion started by: kebabbert
0 Replies
pcram(7D)																 pcram(7D)

NAME
pcram - PCMCIA RAM memory card device driver SYNOPSIS
memory@<socket>/pcram@<technology>,0:c memory@<socket>/pcram@<technology>,0:c,raw The PCMCIA RAM memory card device driver supports disk-like I/O access to any standard PCMCIA static random access memory (SRAM) card and dynamic random access memory (DRAM) card. The driver supports standard PCMCIA SRAM/DRAM cards that contain a Card Information Structure (CIS). RAM card densities in the 512Kilobytes to 64Mbyte range are supported. PRECONFIGURATION
If a PC card memory device is recognized, the pcram device driver is automatically loaded, the physical address allocated, and special files created (if they do not already exist). Known Problems and Limitations The Solaris pcmem driver is not capable of handling "combo" memory cards with multiple types of memory on them (for example, combined SRAM and nonvolatile FLASH). Inserting such a card into a system running the Solaris software may cause a system panic. Because the PC card memory device is designed as a pseudo-floppy diskette type, the only utility that can be used for formatting is fdfor- mat(1). CONFIGURATION
Configuration topics include initial installation and configuration, identifying an unrecognized device, special files, using PC card mem- ory devices, and hot-plugging. Initial Installation and Configuration 1. Install the Solaris software. 2. Boot the system. 3. Insert the card. Identifying an Unrecognized Device If you insert a memory device and it is not recognized (no special files created), use the prtconf command. 1. Become root. 2. Run the prtconf -D command to display the configuration recognized by the system. A recognized device will appear in the prtconf out- put. For example: # prtconf -D . . . pcic, instance #0 (driver name: pcic) . . . memory, instance #0 (driver name: pcmem) pcram, instance #0 (driver name: pcram) 3. If your memory device does not appear at the end of the prtconf output, it is not supported and cannot be used with the pcram driver. Special Files The special files created for PC card memory devices act like disks and have names in the form /dev/dsk/c#t#d#p# or /dev/dsk/c#t#d#s#. Abbreviations used in the names are: o c# Controller # o t# Card technology type #, defined as follows: 0 Null--no device 1 ROM 2 OTPROM (One Time PROM) 3 UV EPROM 4 EEPROM 5 Flash EPROM 6 SRAM 7 DRAM o d# Device region of type #, usually zero o p# fdisk partition # o s# Solaris slice # Note - A device name can be specified either by a partition name (p#) or a slice name (s#), but not both. Using PC Card Memory Devices Since the Solaris Volume Management software recognizes PC Card memory devices, no special vold configuration is required. If you do not want to use vold to manage your PC card memory devices, comment out the use pcmem line in the /etc/vold.conf file. To comment out a line, insert a # character at the beginning of the line. PC Card memory devices do not need to have file systems on them, though typically, before using a new PC Card memory card, you will want to create a file system on it. DOS PCFS is the best format to use. (You can use virtually any file system format on a PC card memory card, but most other file system formats are platform-dependent, making them unsuitable for moving data between different types of machines. See "Using a PCMCIA Memory Card" in the OpenWindows Advanced User's Guide.) Note - If you want to redirect the output of a tar command (or dd or cpio) to a PC card memory device, first create a file system on the card, using the fdformat(1) command without arguments. The card must be reformatted before it can be written on again. Hot-Plugging If a memory card is removed while in use, the device driver returns errors until the memory card is inserted into the appropriate socket. Close and reopen the device with the card reinserted, and the memory card will work. o If you remove the card while in use as a file system, unmount the file system using the umount command. Then reinsert the card and remount the file system using the mount command. o If you remove the card and interrupt a tar or cpio process, stop the process, reinsert the card, and restart the process. /kernel/drv/pcram pcram driver /dev/dsk/cntndnsn block files /dev/rdsk/cntndnsn raw fileswhere: cn controller n tn technology type n 0x1ROM,0x2OTPROM,0x3EPROM, 0x4EEPROM,0x5FLASH,0x6SRAM, 0x7DRAM dn technology region in type n sn slice n fdformat(1), pcmcia(7D), dkio(7I), pcmem(7D) 23 Oct 2000 pcram(7D)
All times are GMT -4. The time now is 08:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy