FC3 and 440GX
by Alex F. Evonosky
Anyone know why FC3 is not working on an Intel 440GX anymore? FC1 did
not work, yet FC2 did (and PERFECTLY); yet FC3 is doing the same thing
FC1 did..
Detects the AIC 7xxx SCSI drives, then hangs... Basically states "no
hard drives found"; when FC2 is actually on the drives.
lspci shows:
00:00.0 Host bridge: Intel Corp. 440GX - 82443GX Host bridge
00:01.0 PCI bridge: Intel Corp. 440GX - 82443GX AGP bridge
00:02.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03)
00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:08.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone]
(rev 24)
00:0a.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone]
(rev 30)
00:0c.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP
1X (rev 5c)
02:04.0 SCSI storage controller: Adaptec AHA-2940U2/U2W / 7890/7891
02:06.0 SCSI storage controller: Adaptec AIC-7860 (rev 03)
02:0a.0 PCI bridge: Intel Corp. 80960RP [i960 RP Microprocessor/Bridge]
(rev 03)
02:0a.1 I2O: Intel Corp. 80960RP [i960RP Microprocessor] (rev 03)
Thanks!
Alex
18 years, 10 months
Re: FC3 mediacheck
by Erik Hemdal
> >
> >>md5sum -c MD5SUM
> >>
> >>I've already indicated this once. After successful MD5SUM check - boot
> >>with 'linux ide=nodma' and then do the MediaCheck.)
I think this comment was from Satish about ide=nodma. Why is that
necessary? I've encountered the mediacheck failures similarly for the
first time ever. If the drive operates normally, why do we need nodma
in order to check only disk2 and disk3 of the CD set?
I'm not intending this as disrespectful to anyone; I'm truly curious
about it. Out of the four install images, all four pass the MD5
checksum test, and two out of four pass the mediacheck. On my CD
writer, cdrecord reports that the buffer was always adequately filled
and burnfree protection was never needed. So assuming the integrity of
the media is OK (seems to be, since cdrecord reports no errors and the
CD is readable), I'd suspect a problem with the original ISO image.
Whether you use DMA or not on your drive doesn't seem to have any
bearing on things....else other I/O would have trouble too.
Am I missing something?
Erik
> >>
18 years, 11 months
ATI drivers
by Dylan Parry
Hi,
I know the proccess has been covered to death in this list, but has anyone
taken the time to write a tutorial explaining how to install the ATI
drivers (the ones for Radeon and up) from the ATI website?
--
Dylan Parry
http://www.webpageworkshop.co.uk - FREE Web tutorials and references
18 years, 11 months
software to read BIOS values
by dballester＠kernpharma.com
Hi to all:
Some time ago I saw a Linux application capable to read BIOS values,
something like <Register> <Content> . Now i don't remember where andf when
i saw this app, and google can't help me very much.
May be the reference was done here in this list. Anybofy remeber it,
or knows what I am talking about?
As usual, a lot of TIAs
David Ballester Montolio
GNU/Linux user #206389
GNU/Linux - Unices Sysadmin
Oracle DBA
SAP-BC
Kern Pharma - Grupo Indukern
www.kernpharma.com
18 years, 11 months
FC3 and ATI Digital video
by Gene Czarcinski
I am having problem when I use digital (DVI) versus analog video.
The hardware:
ASUS SK8V motherboard with an Opteron 140 and 2GB ram. The video is an ATI
9100 with both digital and analog video output (radeon driver). The monitor
is a Dell 2000FP (LCD) which can handle both analog and digital (DVI) input
selectable on the monitor. The is also a Belkin Omnicube 4 port KVM.
When I first started using the ASUS/Opteron system in my setup, I found that I
could not use the analog video through the KVM ... the ASUS BIOS "overdrove"
the monitor and it cut out. However, FC1 did work OK for both install and
running using this analog configuration.
My solution to the problem was to not use the analog/KVM setup but instead to
connect the monitor to the ATI 9100 using the digital (DVI) interface and
then use the selection on the monitor to switch to DVI input when I selected
that ASUS/Opteron. This worked fine with FC1 and FC2 (both i386 and x86_64).
I skipped this round of testing so my first exposure to FC3 was the final
release. I first installed it on another system and that went fine. I then
tried installing on the ASUS/Opteron ... oops, black screen and then the
monitor went into powersave mode (turned off). After several tries, I gave
up and did a text everything install. Install and bootup ... oops, X fails
to start again. OK, reboot and come up in non-X (3). I ran
system-config-display from another system via ssh and everything looked like
it configured properly but X did not display.
After some fooling around, I switch to using the analog/KVM setup instead of
the digital (DVI) setup. That worked fine. With this setup I also then
installed the x86_64 FC3 and it worked fine too.
Bugzilla: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139023
I noticed some laptops are also having problems and wonder if that problem is
related.
Question: Is anyone using digital (DVI) video, an ATI video card and the
radeon driver? Does it work? IS anyone having problems?
--
Gene
19 years, 1 month
2GB limit on samba and nfs?
by Mike Burger
Sorry for the cross post, but the environment calls for it.
I'm running a RHL9 server, and an FC2 client.
Whether by NFS or SMB, I'm running into the same problem.
On my FC2 client system, I'm trying to create a 3.5GB file on the RHL9 based
server. Every time I try, though, I get stuck at the 2GB mark.
At present, I'm attempting to do this via x-cd-roast, which, of course, makes
use of cdrecord(-prodvd).
I'm stuck...I've got the ProDVD key working, as I'm writing more than 1GB,
and I'm not aware of any limitations on x-cd-roast. The mounted filesystem
has 40+GB free on it, so that's not an issue, and I'm running SGI's XFS, to
which I've written files larger than 2GB, before...but directly on the
RHL9 system, as opposed to via networked filesystem.
The system is up to date, as I'm using apt-get against the fedoralegacy
servers for the RHL9 system, and am using both up2date and apt-get for the
FC2 system.
I'm at a bit of an impasse.
Is anyone aware of nfs/smbfs limits that I should be aware of?
19 years, 1 month
CD burning problem
by jery_wang
Hi All,
Here I am, back with another problem. I can't seem to burn CD's with FC3. I've tried the default Gnome burner, k3b and xcdroast, all with no luck. I was beginning to think that it was a hardware problem, but when I booted back to FC2, I was able to burn OK. Running cdrecord --scanbus gives me the following:
[dishawjp@eunix ~]$ cdrecord --scanbus
Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla
Note: The author of cdrecord should not be bothered with problems in this version.
scsidev: 'ATA'
devname: 'ATA'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling').
scsibus0:
0,0,0 0) 'ATAPI ' 'DVD-ROM 16X ' '582F' Removable CD-ROM
0,1,0 1) 'MSI ' 'CD-RW M$-8348 ' '120D' Removable CD-ROM
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
[dishawjp@eunix ~]$
Which would seem to indicate that cdrecord can find the device. But issuing the following command for cdrecord gives me the following output:
[dishawjp@eunix ~]$ cdrecord -v -eject speed=8 /media/cdrecorder /home/dishawjp/docs/
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla
Note: The author of cdrecord should not be bothered with problems in this version.
TOC Type: 1 = CD-ROM
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling').
Driveropts: 'burnfree'
SCSI buffer size: 64512
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'ATAPI '
Identifikation : 'DVD-ROM 16X '
Revision : '582F'
Device seems to be: Generic mmc2 DVD-ROM.
Current: 0x0000
Profile: 0x0010
Profile: 0x0008
cdrecord: Sorry, no CD/DVD-Recorder or unsupported CD/DVD-Recorder found on this target.
[dishawjp@eunix ~]$ cdrecord -v -eject speed=8 /dev/cdrecorder /home/dishawjp/pics/other/
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla
Note: The author of cdrecord should not be bothered with problems in this version.
TOC Type: 1 = CD-ROM
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling').
Driveropts: 'burnfree'
SCSI buffer size: 64512
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'ATAPI '
Identifikation : 'DVD-ROM 16X '
Revision : '582F'
Device seems to be: Generic mmc2 DVD-ROM.
Current: 0x0000
Profile: 0x0010
Profile: 0x0008
cdrecord: Sorry, no CD/DVD-Recorder or unsupported CD/DVD-Recorder found on this target.
I tried both /dev/cdrecorder and /media/cdrecorder and even /dev/hdb as the device in the command with the same results. It appears that the major problem is that it's not finding my cdburner, just my DVD drive. Both drives are ATAPI
Any thoughts on how to get this going? It's not too important for now, but I will want to be able to do backups sometime.
Oh, in case it helps, my fstab is below, it will probably wrap, but maybe give someone a clue anyway:
Code:
@eunix ~]$ more /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/hdd3 swap swap defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/hdb /media/cdrecorder auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
/dev/hda /media/cdrom auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
/dev/fd0 /media/floppy auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
[dishawjp@eunix ~]$
As always, any help greatly appreciated.
Jim
--
This is an email sent via the webforum on http://fcp.homelinux.org
19 years, 1 month
NEC Chipset cardbus USB2 card not working in high speed mode - any hints?
by Charles E. "Rick" Taylor, IV
System:
-------
Thinkpad X22
Fedora Core 3
Kernel 2.6.9-1.698_FC3
Problem:
--------
I've got a Dynex USB2 cardbus card (NEC chipset) that works at high
speed under Fedora Core 1. However, under Fedora Core 3, I can't get high
speed working - which means I can't use my newer CDRW drive, as it wants
to communicate at a minimum of 8X for burning CDRs.
Here's what happens:
dmesg on card insert -
PCI: Enabling device 0000:03:00.2 (0000 -> 0002)
ehci_hcd 0000:03:00.2: EHCI Host Controller
ehci_hcd 0000:03:00.2: irq 11, pci mem e8964000
ehci_hcd 0000:03:00.2: new USB bus registered, assigned bus number 4
ehci_hcd 0000:03:00.2: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 5 ports detected
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ohci_hcd 0000:03:00.0: OHCI Host Controller
PCI: Setting latency timer of device 0000:03:00.0 to 64
ohci_hcd 0000:03:00.0: irq 11, pci mem e886a000
ohci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 5
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 3 ports detected
PCI: Enabling device 0000:03:00.1 (0000 -> 0002)
ohci_hcd 0000:03:00.1: OHCI Host Controller
PCI: Setting latency timer of device 0000:03:00.1 to 64
ohci_hcd 0000:03:00.1: irq 11, pci mem e8a3a000
ohci_hcd 0000:03:00.1: new USB bus registered, assigned bus number 6
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
(Looks normal so far, I think...)
Now, plugging in the CD burner:
dmesg
ehci_hcd 0000:03:00.2: fatal error
ehci_hcd 0000:03:00.2: HC died; cleaning up
ohci_hcd 0000:03:00.1: wakeup
usb 6-1: new full speed USB device using address 2
usb 6-1: not running at top speed; connect to a high speed hub
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: IOMEGA Model: CDDVD482416E23-C Rev: 0037
Type: CD-ROM ANSI SCSI revision: 02
USB Mass Storage device found at 2
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
sr0: scsi3-mmc drive: 24x/48x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
At this point, I can "use" the drive, but only at low speed - meaning I
can't burn anything but CDRW discs (which the drive will burn at 4X).
This drive and card combo works under Fedora Core 1 and will burn at full
speed.
Any hints?
--
--------------------------------------------------------------------
* Charles Taylor <tomalek(a)mindspring.com>
* Chemistry teacher, Linux enthusiast!
--------------------------------------------------------------------
* Web: http://home.mindspring.com/~charletiv/
--------------------------------------------------------------------
19 years, 1 month
Re: FC3 and zip disk
by C. Linus Hicks
On Thu, 2004-11-25 at 01:11 +0000, Donald Ray Lott wrote:
> On Thu, 2004-11-25 at 00:09 +0000, Donald Ray Lott wrote:
> > Hi,
> >
> > I thought I had figured out why my zip drive was not working, but looks
> > like FC3 is tricky!
> >
> > The problem is that now /etc/fstab is re-written every time the system
> > is booted by the hal daemon (hald). /ect/fstab reports the zip drive as
> > hdd when it really is hdd4. You can no longer change the settings
> > in /etc/fstab so how do you get it to work correctly?
> >
> > I can mount hdd4 by command line ok.
>
> man fstab-sync
>
> is called by hald. I tried commands in a terminal but received a
> message to the effect that fstab-sync was nowhere to be found.
> >From there, one is lead to all the files in hald and even to udev.
>
> So, does anyone know the fix?
The executable for fstab-sync is in /usr/sbin which is not typically on
your path unless you are logged in as root. You can get rpm to show you
where the various parts of a package such as hal are installed:
rpm -qil hal
As far as your question about correctly mounting the zip drive, check
out the following URL. It doesn't address exactly your issue, but it
should get you pointed in the right direction.
http://www.redhat.com/archives/fedora-test-list/2004-November/msg00984.html
That combined with the section of the output from 'lshal' pertinent to
your zip drive should give an idea of what needs to happen.
--
C. Linus Hicks <lhicks(a)nc.rr.com>
19 years, 2 months
Attention Fedora Core 3 Radeon users
by Mike A. Harris
Does DRI actually work on Radeon for _anyone_ out there without
crashing either immediately, or within some timeframe?
There are oodles of DRI related radeon bugs, and I'm just trying
to get an idea if it actually works for anyone at all, so we can
decide the best approach to resolving the issues reported so far.
Thanks in advance.
--
Mike A. Harris ftp://people.redhat.com/mharris
OS Systems Engineer - X11 Developer - Red Hat
19 years, 3 months
