Re: FC2T3 Shut down / reboot taking much longer to complete
by A1tmblwd＠netscape.net
Wayne Steenburg <w.steenburg(a)myactv.net> wrote:
>On Sat, 2004-05-01 at 16:54, A1tmblwd(a)netscape.net wrote:
>> Wayne Steenburg <w.steenburg(a)myactv.net> wrote:
>>
>> >On Sat, 2004-05-01 at 01:13, A1tmblwd(a)netscape.net wrote:
>> >> After upgrading from FC1 to FC2T3 the shuting down / reboot process is taking much longer to complete. The slow down begins when the message "Shutting down system logger" appears. Termiation of the process takes a minute or more. Then each of the following processes, "Shutting down interface eth0", "Shutting down loopback interface", and "Stopping iptables" exhibit similar behavior. Termination of these four processes takes minutes to complete. Whereas in the past it took only seconds.
>> >>
>> >> Firewall and iptables are enabled. SELinux is disabled.
>> >>
>> >> What is causing the slowdown? What do I need to do to get back the responsiveness of FC1?
>> >>
>> >If your /home directory is on a separate partition or you have the
>> >diskspace necessary to backup your data, I would try a fresh install
>> >instead of an upgrade.
>> >
>> >
>>
>> Thanks, that's the easy way out. I really want to know what is causing the problem. It's probably something the developers made to accomodate SELinux but haven't quite got working correctly. It would be nice if the developers could fix it before the official release.
>>
>>
>I understand. On my system (Soyo board with a KT-600 chipset) rebooting
>doesn't work. I've tried acpi=off apm=off and such to no avail. I'd
>like to have that work properly as well.
>
I tried using system-config-securitylevel to turn off the firewall. This had no effect on the shutdown time. Found that running the utility re-enabled SELinux (already in bugzilla?) and that I need to "disable" SELinux before exiting the utility. Also disabling SELinux via system-config-securitylevel has not effect. On rebooting SELinux is still active. Need to add "selinux=0" to boot parameters in grub.
I examined /etc/rc.d/init.d/network. The script on my FC2T3 system still has a reference to /etc/modules.conf. I think it should now reference modprobe.conf. Also the script differs from the one on my FC1 system as follows:
114d113
< unset DEVICE TYPE SLAVE BRIDGE
119d117
< unset DEVICE TYPE SLAVE BRIDGE
125d122
< unset DEVICE TYPE SLAVE BRIDGE
130d126
< unset DEVICE TYPE SLAVE BRIDGE
133d128
< unset DEVICE TYPE SLAVE BRIDGE
214d208
< unset DEVICE TYPE BRIDGE
219d212
< unset DEVICE TYPE BRIDGE
224d216
< unset DEVICE TYPE BRIDGE
227d218
< unset DEVICE TYPE BRIDGE
Don't know what it all means. Could be just the differencs in the two motherboards. For all I know anaconda may not have even updated /etc/rc.d/init.d/network. The file has a Jan 28 date.
__________________________________________________________________
Introducing the New Netscape Internet Service.
Only $9.95 a month -- Sign up today at http://isp.netscape.com/register
Netscape. Just the Net You Need.
New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp
20 years, 1 month
konqueror SMB:/ browse error
by ByteEnable
When browsing password protected shares with knoqueror, I get the following
message below:
Internal Error
Please send a full bug report at http://bugs.kde.org
libsmbclient reported an error, but didn't specify what the problem is. This
might indicate a severe problem with your network - but also might indicate a
problem with libsmbclient.
If you want to help us, please provide a tcpdump of the network interface
while you try to browse (be aware that it might contain private data, so
don't post it if you're unsure about that - you can send it privately to the
developers if they ask for it)
Byte
20 years, 1 month
Re: FC2T3 Shut down / reboot taking much longer to complete
by A1tmblwd＠netscape.net
Wayne Steenburg <w.steenburg(a)myactv.net> wrote:
>On Sat, 2004-05-01 at 01:13, A1tmblwd(a)netscape.net wrote:
>> After upgrading from FC1 to FC2T3 the shuting down / reboot process is taking much longer to complete. The slow down begins when the message "Shutting down system logger" appears. Termiation of the process takes a minute or more. Then each of the following processes, "Shutting down interface eth0", "Shutting down loopback interface", and "Stopping iptables" exhibit similar behavior. Termination of these four processes takes minutes to complete. Whereas in the past it took only seconds.
>>
>> Firewall and iptables are enabled. SELinux is disabled.
>>
>> What is causing the slowdown? What do I need to do to get back the responsiveness of FC1?
>>
>If your /home directory is on a separate partition or you have the
>diskspace necessary to backup your data, I would try a fresh install
>instead of an upgrade.
>
>
Thanks, that's the easy way out. I really want to know what is causing the problem. It's probably something the developers made to accomodate SELinux but haven't quite got working correctly. It would be nice if the developers could fix it before the official release.
__________________________________________________________________
Introducing the New Netscape Internet Service.
Only $9.95 a month -- Sign up today at http://isp.netscape.com/register
Netscape. Just the Net You Need.
New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp
20 years, 1 month
OT:: kernel module gui in fedora? ::OT
by Mark Fonnemann
Hello-
please forgive me for being off-topic...
a couple questions:
1. is there any graphical utility to load and unload kernel modules in fedora?
or is insmod, modprobe, and lsmod the only way to go about this?
2. is there any good explanation out (besides the Linux Kernel Module FAQ and
the man pages) about linux kernel modules? i can find a lot of info out there
about kernel module programming but i'd like something more intermediate...
3. is there any documentation about the particular kernel modules installed at
runtime by default?
i'm just trying to learn more about the linux kernel and i'd like to remove
excess kernel modules (if possible) to save memory.. any help would be greatly
appreciated!
thanks,
mark.
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
20 years, 1 month
FC3T3 grub hangs on brand new DELL 8300, fix with some BIOS settings
by Anne & Lynn Wheeler
grub hangs on brand new DELL 8300, BIOS A05, two 250gbyte SATA drives,
SATA raid controller, 4gbyte memory. SATA bios raid configuration not
changed/touched.
install from FC3T3 CDROM works w/o problem .. to simplify things
all defaults used ... with all old partitions deleted.
tested with and w/o BIOS limiting memory to 256mbytes.
grub 0.94 diskette boots (built from a FC3T3 system on a dell 410)
root tab sees fd0 & hd0
root (hd0, sees part0, type ext2f2/0x83 aka /boot
& part1, type unknown/0x82 aka swap
this is /dev/sda, first sata drive
default config puts "/" on /dev/sdb, 2nd sata drive
cdrom linux rescue boots and is able to mount /boot & / and can
access/change files
direct boot from harddisk, results in display "GRUB" and then nothing,
power cycle is required.
with grub diskette and setting root to hd0,0
then any attempt to read file hangs grub solid requiring power cycle.
fstest doesn't turn up anything
ioprobe results in reboot
find a file in (hd0,0) i.e. /boot, hangs and requires power cycle
boot vmlinuz file in (hd0,0) hangs and requires power cycle
slashimage (hd0,0) file hangs and requires power cycle
find a file that doesn't exists, comes back with file not found
if SATA RAID array definitions are deleted, then no drives can be
found by anybody.
so you won't believe the solution. it would appear that FC2T3
ignores the SATA RAID definitions and directly accesses the physical
devices (i.e. /dev/sda & /dev/sdb) ... while GRUB with HD0 ....
(may?) goes thru the SATA RAID controller definition. The master
boot record are enuf the same ... so that booting GRUB from the
harddisk gets it to the point where it says GRUB.
It appears that the work around is to try and make the SATA RAID
definitions match the FC2T3 direct access to the device. In the SATA
RAID BIOS setup, define two separate STRIPE arrays, each with one
physical disk drive.
(re-)install from cdrom, then things boot fine.
20 years, 1 month
Three more test boxes, one new set of problems , one old
by Alan Cox
IBM Thinkpad 600 - updated perfectly. I've not yet checked out all the old
desktop problems I was having to see if they are gone but will do so.
Installer incorrectly spews warnings about geometry matches still. APM auto
suspend stuff doesn't like 2.6 but otherwise is working better RH9, and
definitely better than FC1
Cyrix III with 3ware ATA raid. No problems despite those reported by some
users. Had to specify mem=512M because the BIOS gets the mtrr data wrong
and we don't seem to correct it (thats always been the case). Had to use
text mode because vesa driver on P9100 is broken (again old problems).
Working as well as 2.4/FC1
Dual Opteron with dell obsidian quad ultra80 raid card. This blows up if there
are any volumes on the aacraid, but is fine if the aacraid has no disks.
It also blew up because the old disks I reused to avoid the aacraid both
had a /boot partition on them which it took offence too, and after I fixed
that it offered to upgrade my IA32 distro. I wasn't sure if this was supposed
to work so I hit upgrasde. It flashed something up on screen I couldnt
read and then exited the installer. If I do a new install this problem doesnt
seem to occur
Welsh language stuff also looks ok. Initscripts is short the most recent
po file fixes, up2date is somewhat messed up (but quite frankly its got
critical bugs open since FC1 beta so I don't think anyone cares much). I
guess yum needs translating though.
20 years, 1 month
Bug/status summary from my testing
by Alan Cox
Generally test3 is looking good, even on weirder setups including the
CyrixIII box.
aacraid is broken on AMD64 (#122196)
release notes are broken (typos, and corners wrong at bottom) (#122199)
x86-64 install blows up upgrading x86-32 installation (#122201)
Bogus partition warning (#12204)
Broken display mode options (#122205)
One box needs mtrr fixups (upstream issue)
Queued to retest
- NCR5380 is broken in older FC2test
- Atmel USB wireless is broken in older FC2test
- Acard ATP870U corrupts memory on older FC2test
- 3com 3c590 was not working in FC1/FC2test but was in RH9 or with Becker
driver.
- I2O support is broken (need to also test Markus patches not integrated)
Then on to X stuff - via driver problems, voodoo driver missing etc.
20 years, 1 month
RE: test3 vs make xconfig
by A1tmblwd＠netscape.net
Gene Heskett <gene.heskett(a)verizon.net> wrote:
>Greets all;
>
>I just ran a make xconfig on that fresh install of test3 on my shop
>box as I wanted to turn on a full fledged ISA bus scan since there
>are two custom made 8 bit ISA cards containing a few relays and
>apparently a whole 8 bit wide input port per card, and while I have
>what appears to be normal fonts elsewhere, all I get on the xconfig
>screen are gfx chars, little boxes of various shapes and half,
>quarter, and full moons in a character sized box.
>
>That box isn't on a network allthough it may be eventually when I can
>figure out howto get some cat5 run to the shop building. I hate
>digging ditches, been there, done that once already for power out
>there.
>
>Running gnome of course since there is apparently no terminals
>available if I switchdesk to kde. And it sure don't look like the
>kde I'm looking at here!
>
>How can I fix these fubared characters?
>
>--
>Cheers, Gene
Use qconfig. It's not broken. If you must use xconfig, an anonymous poster in a 2.6.5 kernel forum recommended running qtconfig. Deselect (turn off) the option labeled "Enable Anti-Aliased Font Support (XFT)". It worked for me.
-- Kam Leo
__________________________________________________________________
Introducing the New Netscape Internet Service.
Only $9.95 a month -- Sign up today at http://isp.netscape.com/register
Netscape. Just the Net You Need.
New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp
20 years, 1 month
Synaptics
by Quasar Jarosz
Might be a bad question for this list, but anyone have an experience
getting a synaptics touchpad to work under FC2Tx? I'm about to try, and
just wondered if anyone had any hints.. especally now that we're using the
Xorg xserver.. although i guess they both use the same drivers?
20 years, 1 month
RE: header/RPM mismatch
by Fulko.Hew＠sita.aero
... some context snipped for brevity...
>> If yum is supposed to replace up2date, then its config file, should be a
>> superset
>> of up2date.
>
>Who said yum is supposed to replace up2date?
If yum is not to replace up2date for updating, then why does it exist?
What itch is _it_ scratching that up2date
wouldn't/shouldn't/couldn't scratch?
Or is it another case of 'Not Invented Here' syndrome?
>> After all, they are both supposed to do the same thing.
>
>Again, KDE vs. Gnome, vi vs. emacs, etc.
but KDE and Gnome do _not_ do the same thing, and they do not
use the same config files, and they are not infered to work together
(except for the rhn applet that does work on both task bars.)
As for vi vrs emacs, they both operate on the same kind text files,
and when your done editing your file with one, the file is still readable
and usable by the other editor, so thats not a valid analogy.
>> The bigger issues is that headers are saved in two different directories
>> on your system, so its guaranteed to get out of sync.
>
>Huh? Neither needs the others headers.
Its more like neither _uses_ the other's headers...
hence the duplication and inconsistency problems that result.
(see the final comment).
>> c) If you decide to carry on with up2date, you now have to ignore all
>> of the GPG errors, because of... (well I don't know).
>
>Of install the correct GPG keys...
What are the correct keys?
I installed test 3 from the release CDs and went through the
upgrade process. Are there other manual, un-documented steps
that need to be performed to get rid of these GPG errors?
If so, please give me a link.
>> e) Ohh, sometimes up2date hangs... Well just re-install, maybe it'll
>> work.
>
>Have a reproducible situation? A bug number? I've been using up2date on
>FC1, FC2Test2, and FC2Test3 and I don't recall any hangs.
Yes, 100% reproducible since yesterdays's daily RPM fetch.
... while typing this message, I tried it again, and it no longer
hangs. :-( Maybe some of my earlier playing with the header
directories has resolved something... I don't know....
But the 'there are 2 packages to fetch, but you can only select
one of them' issue still remains.
>> d) If you get frustrated by the now broken up2date and the GPG issues
>> you resort to using yum. But sometimes _it_ lies.
>
>So if "you resort to using yum" why do you think it should replace
up2date?
Because I don't know which tool I _should_ be using. :-(
I'd like to use the rhn_applet and up2date because:
a) thats what I used with RH7.x, 8.x, 9.x
b) it always _used_ to work
c) its on the desktop and its pretty,
d) and most of the time it works (or at least it did,
ignoring the 'size reporting' issue and the "GPG error' issues.
But now that doesn't work so I have to use yum,
which gets me a 'little' further.
>> So in the end you don't know what you've got,
>> who's wrong, whats wrong
>> or where and how to fix it.
>
>They all use the same rpm database.
Sorry, I was talking about the various update notice facilities
and updating processes, not their end product.
>> I don't mind having choices, but at least one of those choices should
>> work, and if the others don't. Then they shouldn't be supplied.
>
>Both work for me. YMMV.
And both used to work for me too. Its just that as the days
go by, and as we moved from test2 to test3, things are
degenerating (here).
... snip ...
>I'm sorry, if you are not interested in new features why are you running a
>test release?
Because I want some of those new feature, but call me selfish...
I also don't want some of the old features broken. ;-)
Like up2date, or USB hotplug.
>>So set up multiple rsync jobs and have a human check that the first is
>> done?
>>
>> No, set up one job that rsyncs the RPMs, and then rsyncs the headers.
>
>And the case of headers being release on the main site after the first job
>is started is resolved how?
If there is a dependency and synchronization requirement on the
updating facility, then rsync is 'inappropriate' to use to maintain
mirrors in order to ensure 'system integrity'.
>>>Yes, I think you should pick one and throw the rest away.
>>
>> OK, which one? Which one works? ...Neither.
>
>In my experience both.
That _used_ to be my experience, but since the virgin install of
test3, this no longer seems to be the case (and its not just me,
count at least 2 occurances here in Canada).
> If you are trying to run up2date and yum at the same time you might have
> just answered your own question.
Then I'm back to asking which one _should_ I be using?
... snip....
>> But neither of them use the same front end database and neither
>> seem to work right... anymore.
>
>Both use a yum repo and both put transactions into the RPM database. What
>database are you talking about?
The directories where current and ancient headers and rpms are saved:
/var/spool/up2date
/var/cache/yum/development/headers
20 years, 1 month
