USB issues in non-upgraded kernel
by Rio Baan
I haven't updated my test2 kernel (it is still the vanilla ISO test2 one),
so I *possibily* this bug has already been fixed.... according to bugzilla,
but I can't be sure, so I'll throw it out here.
Anyway, I'm having difficulty unmounting a flash drive under
2.6.3-2.1.253.2.1
Plugging in the USB-key gives me some kernel info, and after creating a
mount point for it and tweaking fstab (/dev/sdb1 /mnt/flash vfat
noauto,user,umask=0 0 0), no problem. When I am finished with it, I cannot
seem to unmount it - even when I am sure that there is no continued access
to the device. Instead, all I get is:
umount: /mnt/flash : device is busy
umount: /mnt/flash : device is busy
And what's funny is that umount feels that it has to print this info out
twice.
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
20 years, 1 month
Tester Hardware Database and ID
by Will H. Backman
I seem to remember some tool from redhat that would gather system info
for support purposes. It gathered all kinds of stuff, and wrapped it up
into a compressed package. Would it make sense to use something like
this to have a central place for testers to submit their hardware specs
and receive a "test machine ID"? When sending mail or bugzilla info,
one could include that ID. Others could then look up hardware info.
Just a thought.
--
Will Backman <whb(a)ceimaine.org>
Coastal Enterprises, Inc.
20 years, 1 month
FC2T2 DVD - boots, but no media check
by Chris Adams
I successfully booted both the FC2T2 DVD and CD images on my notebook
(Fujitsu Lifebook C2010). The CD comes up and prompts to check the
media, but the DVD image does not. Shouldn't it?
Bugzilla #119490
--
Chris Adams <cmadams(a)hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
20 years, 1 month
Re: SATA errors linger in test2
by Rio Baan
>Can you boot single CPU kernel?
Nope! Can't get FC test2 first booting at all on either kernel. Install was
painless though.
>If so - try building a vanilla kernel with SMP support and booting that.
>That may give a clue as to who's fault the panic us (patches or vanilla)
I'll compile a vanilla kernel using the latest 2.6 from kernel.org on
another machine and use the config file from test2. I'll try and drop that
into my system and see what it does.
>Also if you can boot single cpu - maybe the 2.4 fedora kernel has the
>issue resolved - so you could update to that.
I haven't tried, but when I had a P4 2.4A CPU in the same hardware (I only
swapped the CPU recently) FC1 had the same problem. It's definitely SATA
RAID related because I can get the machine to boot if I just unplug the
drives from the RAID controller on the motherboard. Still, I don't feel that
I should have to open my case everytime I want to boot into FC.
Also with the acpi options..... these are directives that I put into GRUB
before booting, right? I've done this before in LILO, but I'm not sure how
it works out in GRUB.
_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
20 years, 1 month
A followup report
by Jonathan Corbet
Previously I had reported on my x86_64 upgrade from FC1, which had croaked
with a python error...
...as I threatened, I went ahead and did a clean install on the system,
seeing as it was hosed anyway. It all seemed to go well; no python crashes
this time around.
X is still completely screwed up (on my Radeon 9200SE) with the FC2t2
kernel; I get a confused mess on the screen and no response to the
keyboard. The pointer works, though, FWIW.
When I boot 2.6.5-rc3, after ensuring that the radeon and agpgart modules
are loaded, X works just fine. At least, it did after I brought in an old
config file; it wasn't set up to run in 1600x1200, even though the (newly
renamed, it seems) system-config-display utility said it was going to.
Incidentally, that tool doesn't know about my ViewSonic A110 monitor. Must
be time to get one of those nice LCD panels.
Ah, yes, I had to turn off kudzu to get the system to boot with the FC2t2
kernel; otherwise I get an oops in sys_delete_module and everything comes
to a stop. I have no clue of which module it was trying to unload.
Anyway, I'm running to the point where I don't think I'll retreat to FC1.
We'll see what I run into next...
jon
Jonathan Corbet
Executive editor, LWN.net
corbet(a)lwn.net
20 years, 1 month
Re: Unknown GPG signatures
by Anthony Richardella
How do I do this? I'm not to familiar with gpg.
Anthony
>I solved my unknown signature problems by importing all of
>the signatures in /usr/share/doc/fedora-release.
On Thu, 2004-04-01 at 10:44, Anthony Richardella wrote:
> Should I worry about packages I download using up2date that
> give an "unknown GPG signature" error? After installing
Test
> 2 and running up2date there's about 20 packages that give
> this error.
20 years, 1 month
Whither nmh?
by Jonathan Corbet
Interesting...it appears that nmh got dropped out of FC2? Was that a
deliberate decision? There was, at least, one user left... Guess it's
time for a "grumpy editor" column on mail clients.
jon
Jonathan Corbet
Executive editor, LWN.net
corbet(a)lwn.net
20 years, 1 month
LVM problems in FC2 test 2
by Carlos Villegas
LVM did improve from FC2 test 1 to test 2, but I'm still having
serious problems with it upon boot:
The system was kickstarted and the partitions were built from
scratch (not reused), the relevant ks.cfg entries are:
clearpart --all --initlabel
part pv.01 --fstype ext3 --size 10241 --grow
volgroup largespace pv.01
logvol /tmp --vgname largespace --size 2048 --name tmp
/ is in a normal partition (not LVM), as is /boot and /var
The box is a dual opteron, and all this is for the x86_64
version.
Anaconda worked flawlessly. During the first reboot I got
problems finding / (yes, the root filesystem), getting a
nice kernel panic. After some hacking around, I found that for
some reason the LVM space was an ext3 filesystem also labeled
"/" as was the / partition, and so the kernel argument
"root=LABEL=/" was failing due to duplicate / entries.
I booted in single user mode and changed the label of the LVM
space to /LVM, however it still fails on the fsck, because the
devices don't exist (/dev/largespace/tmp) in the example above.
Using the command lvm in it's various incantations shows me that
the LVM groups and partitions are actually there, and correct.
As with test 1 I'm not sure which package is responsible for
this bug (initscripts?, dev?, kernel?) please some one tell me
or report it to the appropiate place.
I disabled selinux.
Carlos
20 years, 1 month
C2T2 -- X from older RedHat install, external WWW access
by Darryl Gamble
I've just installed Fedora C2T2 and it is working quite well for most
things.
I have two issues that have me stumped.
1. Trying to start an xterm on fedora_test from an old RedHat 7.2
installation. I get the message:
"xterm Xt error: Can't open display <fedora_test>:0"
Is this an X authentication error related to having older versions
writing to Xauth? Is there an easy fix for it?
BTW When I ssh to the same machine and do an xterm through DISPLAY
<redhat_72>:10.0 it works properly.
2. Access to external web sites fails. Web sites on the same subnet
work alright and I am able to ping external web site names.
However telnet's to port 80 or mozilla web access fails with a timeout
(either by name or bu IP address).
Interestingly I was working fine under C2T1 *until* I upgraded my kernel
through up2date from the 2.6.1 release to the 2.6.3 release (the default
kernel in C2T2). (BTW I have set selinux=disabled for these tests and
disabled the firewall).
What should I look at in the kernel that might be causing this issue?
(an IPv6 vs IPv4 problem?)
I am currently using kernel 2.6.3-2.1.253.2.1 and can not get external
access. Can someone help me out and point me in the right direction?
Thank you,
Darryl
20 years, 1 month
Rhythmbox /gstreamer won't use esd?
by Steve Bergman
I've not used rhythmbox before, so I don't know if this is an
FC2-test2ism or not. But when I try to play something with rhythmbox,
it complains that something else is already using the alsa device. I'm
actually on a remote X terminal, so I have set ESPEAKER and gone into
the gconf editor and set audiosink to esdsink. This has no effect. I
still get the error about alsa.
-Steve
20 years, 1 month
