another radeon error on newer card - laptop
by Jim Cornette
I was testing the latest xorg-x11 version on my laptop to ensure that
there were no incorporated changes that would effect my computer when
FC3 becomes a reality. I found that after awhile running, I'd get fifo
errors and would have to either reset the computer or if lucky, just
have to reboot or wait long enough for it to exit.
Anyway, attached to the xorg-x11 bug submitted for the radeon 7200 card
is the results encountered with this later version radeon card.
lspci shows this card as below. lspci -vvv results are attached to the
bug report.
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility
U1
This bug seemed to be triggered when using mozilla mail. Therefore, I'm
using netscape mail to respond. I tried to use evo, but the default
email addy for outgoing got in the way again.
Jim
https://freedesktop.org/bugzilla/show_bug.cgi?id=1384
--
Ha. For once you're both wrong but not where you are thinking.
- Larry McVoy to Linus Torvalds on linux-kernel
19 years, 8 months
Re: Does udev make system unbootable?
by Chris Ha
My problem also gone with .541 kernel, but one more
thing... VMWare. I am not sure this is related to /dev
issue, but seems like that VMware looses it's
configuration (Network and Sound under /dev) at every
reboot.
Thanks,
atie
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
19 years, 8 months
Re: fedora-test-list Digest, Vol 7, Issue 44
by Mickey Stein
>
>
> n Saturday 18 September 2004 13:06, Dwaine Garden wrote:
>
>>>Mike Klinke wrote:
>>
>>
>>>>>On Saturday 18 September 2004 11:35, DG wrote:
>>>>>
>>>>>
>>>>>
>>>>>Two things I did that led to my inability to boot was using the
>>>>>--noudev switch on the mkinitrd command line and in the udev
>>>>>configuration file:
>>>>>
>>>>>/etc/udev/udev.conf
>>>>>
>>>>>I had the line:
>>>>>
>>>>>UDEV_INITRD="no"
>>>>>
>>>>>
>>>>>After changing that line to:
>>>>>
>>>>>UDEV_INITRD="yes"
>>>>>
>>>>>and then rebuilding the initrd*.img file without the --noudev
>>>>> switch I could then boot just fine into the .541 kernel.
>>>>>
>>>>>Regards, Mike Klinke
>>>
>>>
>>>
>>>I'm ok there. the UDEV_INITRD='yes' is set fine. My fedora .541
>>>kernel boots ok. But the plain kernel.org kernel
>>>does not. Ummm... I must be missing something.
>>>
>>>Dwaine.
>>
>>
I've had this problem now and then with udev enabled (using the latest
rawhide tree of course). Here's a few things you might try:
(my examples are using kernel.org kernel 2.6.9-rc2 at the moment, so
whatever I write will reflect that. Change to fit your setup)
- Kernel.org kernels (2.6+ anway) work ok with udev but you'd at least
have to have this one option enabled for it to work:
$ grep -i hotplug /usr/src/linux-2.6.9-rc2/.config
CONFIG_HOTPLUG=y
I just use the old $make xconfig from the new kernel directory while
in X and search around for that but you can also just plug it in manually.
That's pretty basic.
- Fedora's version of udev has given me some troubles (udev-030-26) that
appear to come as a result of a buggy /sbin/start_udev script. (buggy in
some configurations probably, but not all). In my case, it just didn't
create the new devices, period. I switched over to using the kernel.org
latest udev (udev-032), building it and installing it, and making sure
that the scripts and binaries are installed manually afterwards. Udev is
definitely a work-in-progress and fedora does things it's own way, so
this takes a little watchful doing to get working at times. By the way,
the start_udev script is actually , I think, in a subdirectory of
udev-032 called extras. Copy it over /sbin/start_udev.
- So how would you do all of this on a system that won't boot? I think I
did it all on a non-booting system using an fc3 cd #1 i'd made as the
boot disk and booting via "linux rescue", then after bootup, changing
root (chroot /mnt/sysimage) as directed by the bootup process. I don't
use any ramdisk (from mkinitrd etc) and I'm sure that could be a point
of contention, but for me, I only had to be sure that the
kernel.org/kernel/utils version of udev-032 was built and installed and
that a "$chkconfig --list | grep -i hotplug" showed that hotplug was
enabled on startup.
- the statements in recent initscripts rc.sysinit file of the nature of
". /etc/udev/udev.conf; /sbin/start_udev" should be following (not
necessarily immediately) the mounting of /sys & /proc filesystems. You
should see output to the tune of "creating udev devices.... complete"
right before init 3 is invoked. (or init 5, whatever you have setup).
- Keep the /etc/udev/udev.conf and /etc/udev/rules.d/50*.rules files
that came out fedora's udev package because fedora needs them to start
udev. (note a section in the middle of that file "
# Additional configuration options added by Red Hat
####################################################
- good luck. I'm sure I could be forgetting something, but this is
pretty much what worked for me and timewise, it really beat restoring a
backup or any other alterative. Reinstalling *dev*, running MAKEDEV will
basically only create a single dev at a time and you have to feed it
everything. The start_udev script if its the correct one, will invoke it
to make every dev based on your configuration. Allowing for mistakes,
fumbles, and just flailing like mad, this should take about 30 minutes
to fix. Even though the udev documentation is pretty convoluted and
obtuse, its a must-read if you ever want to get the udev rules and
permissions under hand. If this , by some miracle, happens to help, but
you then get into a race condition problem between hald and udev or see
udev processes using a lot of cpu, I've got just the fedora bugzilla
report for you ;)
---------
19 years, 8 months
Does udev make system unbootable?
by Chris Ha
I think I got udev package onto my fc3 t1 box by
updating all the packages from yesterday(09/17/04)'s
development tree. After that, it manages my system
unbootable as below.
At boot message :
warning : unable to open an initial console
(just 2 more lines about SElinux - I don't recall)
after these messages, booting process hangs there.
If someone knows about how to fix, could you please
help me out?
I have checked /dev directory using Knoppix, and seems
like many of device files are not there. I'd like to
know how to fix, specially with Knoppix if possible,
of course other ways of fixing are welcomed.
Thanks,
atie
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
19 years, 8 months
Smashing my head against the Wall - Hanging Kernel Booting
by Dwaine Garden
I just yumed against the latest version of the development tree. As of
the 17th.
I'm having a problem booting with a compiled version of the standard
kernel from kernel.org.
It's 2.6.8.1.
After the initialization of the usb stuff. The cpu goes full steam and
the machine just sits there. I did not have any problem with compiling
a kernel before. So I though I have something wrong with my grub.conf.
Just to let you know, kernel 2.6.8-1.541 boots fine. But since I do
development work with the usbvision driver. I use the base kernel from
kernel.org.
What am I missing? I did turn off the SCSI stuff, because I thought it
was the problem. There is no indication that there is a problem. Just
stops booting and the cursor sits there.
Thanks...
Dwaine.
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,1)
# kernel /vmlinuz-version ro root=/dev/hda3
# initrd /initrd-version.img
#boot=/dev/hda
default=1
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz
title Fedora Core (2.6.8.1)
root (hd0,1)
kernel /linux-2.6.8.1 ro root=/dev/hda3 rhgb quiet
title Fedora Core (2.6.8-1.541)
root (hd0,1)
kernel /vmlinuz-2.6.8-1.541 ro root=LABEL=/1 rhgb quiet
initrd /initrd-2.6.8-1.541.img
19 years, 8 months
Multi Wan Question
by Tiernan OToole
I am hoping someone can help me here. I am looking for a way to have
multiple (2 in this case) WAN connections (Cable modems, again in my
case) on a Linux box. I have seen other ideas around, but I hope that
Fedora has the solution I need: ease of setup. I don't have a lot of
time to be messing with the system, so I would like it to be installed
and forgotten. Maybe one or two tweaks but with a GUI and quick.
Thanks in advance.
Tiernan O'Toole, MCP
www.lotas-smartman.net
www.the-hairy-one.com
www.lsn-blog.tk
19 years, 8 months
eth1 getting moved to eth0
by Martin
if have two network interfaces, eth0 which i want to be
the hardwired motherboard device, and eth1 which should
be the wireless device. it has been working fine for some
months, but something got corrupted and I just can't get
things working again.
the wireless device wants to come up on eth0, despite
what's in /etc/modeprobe.conf and /etc/sysconfig/hwconf.
all the files in /etc/sysconfig/networking and network-scripts
seems to be correct... that is have eth0 where i expect and
eth1 where i expect.
Am I missing some other configuration files that controls which
interface gets bound to eth0 or eth1?
and also, every now and then kudzu thinks i've removed and then
re-added the wireless device, and then i have to end up editing
all these config files to get things back to where they were. (
and then kudzu still wants to change things).
I have fedora core 2 + patches. kudzu 1.1.68.2-1
-Marty
19 years, 8 months
Anyone else finding a problem with transcode?
by Paul F. Johnson
Hi,
I'm using FC3t2 (well, t1 with every update running on it, so I'm
guessing that is more or less t2).
I've had transcode running on this box since it was a vanilla FC2
machine without a problem - until last week when it will start up, but
completely fail to find any of the conversion modules.
Is anyone else seeing this problem or is it my system?
TTFN
Paul
--
Homer: Donut?
Lisa: No, thanks. Do you have any fruit?
Homer: This has purple stuff inside. Purple is a fruit.
19 years, 8 months
Re: no USB jump/flash drive support yet
by Fulko.Hew@sita.aero
"Noah Silva [Mailing list]" <nsilva-list(a)aoi.atari-source.com>@redhat.com
on 09/17/2004 02:18:00 PM said:
> The DRIVE should show up as /dev/sda, the data partition should usually
be
> /dev/sda1. Unfortunately my [sony] memory stick seems not to work under
> FC2 at least, but it doesn't cause hanging problems, it just doesn't work
> at all.
It may be due to the fact that FC2 added ACPI support and your machine
has a buggy ACPI BIOS (like mine did). All my USB stuff stopped working
when I switched to FC2.
Go back throught the archives and look for USB and ACPI for _my_ problem
and solution.
> > Tom,
> >
> > Both of my thumb drives appear as /dev/sda and work perfectly. Other
> > folks have reported their thumb drives appear as /dev/sda1. And there
> > are some truly evil thumb drives that require Windows security drivers
> > to access them. Has that possibility been ruled out?
19 years, 8 months
Re: no USB jump/flash drive support yet
by t l
The only additional info I've been able to get
is by running 'lsusb'. It lists the USB Flash
drive that usbcore fails to probe correctly.
Here is the output from 'lsusb':
Bus 004 Device 004: ID 08ec:0010 M-Systems Flash Disk Pioneers DiskOnKey
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 03f0:1e11 Hewlett-Packard
Bus 001 Device 002: ID 0409:0058 NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 0000:0000
tom
------------------------------------
* From: TGS <spam tachegroup com>
Same exact problem here.
I am able to use some USB Flash drives without issue, but some fail. The
failures lock up the whole mount subsystem capability, and the only way to
fix it is to restart. My errors are just like the below. Is there a way to
gather detailed information for the failed devices?
--
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
19 years, 8 months