RE: Installation of FCT2: GRUB interactive on 1st install and GRUB hangs on 2nd install
by Dan Thurman
Hi,
Yes, I did that. It did not work. I am re-installing for the third
time taking all of the fedora defaults (it sets the paritions of
MBR to /dev/hda, /boot to /dev/hda1, / and swap to /hdb1 and I manually
selected the packages for server setup. Lets see how that flys....
I noticed tho, that grub-install and grub (interactive) NEVER touches
the /boot/grub.conf file... hmmmmm. So if your grub.conf is missing
or corrupted... oh gosh darn, too bad.
Note: previously I fiddled with the paritions and noticed that the
difference
is that / was on /dev/hdb3 parition with no active set and the default
suggested
/ is on /dev/hdb1, with active partition set. I took the suggested
/boot to be
/dev/hda1 with MBR for /dev/hda (so, I always took the default). I am
wondering
if the / partition *has* to be in the first partition of any drive and
set to active
as I know that /boot has to be the first partition and set to active. I
thought
that / parition can be anywhere it wants to be.
Sheesh, I spent all day Sat/Sun and getting nowhere with FCT2!
Bad-Karma day I suppose.
Dan
-----Original Message-----
From: Chuck Mead [mailto:csm@moongroup.com]
Sent: Sunday, May 02, 2004 8:07 PM
To: For testers of Fedora Core development releases
Subject: Re: Installation of FC T2: GRUB interactive on1st
installandGRUBhangon 2nd install
Daniel B. Thurman wrote:
> Hi,
>
> I tried EVERYTHING from grub-install, to interactive grub
> so something is very wrong and I am unable to understand
> it. The grub.conf file is correct, the MBR is written
> on the same drive as the /boot (although / is on a different
> drive, non-active parition) so I have no idea what the problem
> is. Heck, I have installed RH MANY times with no problems,
> so why is FCT2 failing for me?
>
> Any ideas???
Does it boot to this:
grub>
and then stop?
If so you can try this...
Type the following at the grub prompt:
root (hd0,0) <then hit enter>
setup (hd0) <then hit enter>
If you get no errors then you can reboot and see if it works.
--
csm(a)moongroup.com, head geek
http://moongroup.com
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-test-list
20 years
test3 DVD ISO not a multiple of 32KiB blocks
by James Ralston
FC2-test2-i386-DVD.iso was 4306010112 bytes, which is a multiple of
32KiB (specifically, 4306010112 bytes = 131409 32KiB-sized blocks).
However, FC2-test3-i386-DVD.iso is 4379752448 bytes, which is *not* a
multiple of 32KiB:
$ factor 4379752448
4379752448: 2 2 2 2 2 2 2 2 2 2 2 2138551
Therefore, growisofs pads it by 18432 bytes up to 4379770880 bytes
(133660 32KiB-sized blocks) when burning it. This makes it a pain to
verify the MD5 checksums; instead of being able to just run md5sum on
the device (e.g., "md5sum /dev/hdc"), you have to use dd to read only
the size of the ISO (without the pad).
Was FC2-test3-i386-DVD.iso not being a multiple of 32KiB blocks in
size intentional, or just an oversight? And will the DVD ISO for FC2
final be a multiple of 32KiB blocks in length?
--
James Ralston, Information Technology
Software Engineering Institute
Carnegie Mellon University, Pittsburgh, PA, USA
20 years
libusb and scanners - scanner module removed in 2.6 kernel
by Jim Cornette
I was trying to use bugzilla and it did not work correctly. Anyway, the
version of SANE-Backends is 1.0.13 and there was a lead that a hotplug
wrapper might be needed to fix the scanner problem using the 2.6 kernel
and scanners.
By checking out the SANE webpage, I found the below information. This is
a recent change. Is this USB hotplugging fix what is needed?
Currently, I run a chown user /proc/bus/usb/001/004 in my /etc/rc.local
file to get my scanner working on boot. I leave it plugged into the same
usb port.
any help?
Jim
Latest News
2004-05-01: SANE-Backends-1.0.14 has been released
* New backend: u12
* Updated backends: artec, artec_eplus48u, as6e, avision,
canon630u, canon_pp, epson, fujitsu, gphoto2, gt68xx, hp, matsushita,
mustek, mustek_pp, mustek_usb, plustek, plustek_pp, sm3600, snapscan,
teco1, teco2, u12, umax, umax_pp, v4l.
* Added scripts for USB hotplugging (Linux)
* Added Danish translation. Updated other translations.
* sane-find-scanner knows about more chipsets now.
* Portability fixes (especially for MacOS X, NetBSD, OpenBSD, and
OS/2).
* Build system fixes.
* Documentation updates.
* Bugfixes.
2004-04-21: If you have trouble with SANE and USB scanners when updating
from Linux 2.4 to 2.6 please read README.linux first.
http://www.sane-project.org/README.linux
excerpt:
With Linux 2.4.* you could either use the kernel scanner module or libusb to
access USB scanners. In Linux 2.6.4 the kernel scanner module was removed.
Therefore with this and later kernels libusb must be used.
While SANE automatically uses libusb when the library and its header
file were
present during the build of sane-backends, setting permissions will require
some attention.
The device files used by libusb are located in /proc/bus/usb/
(e.g. /proc/bus/usb/001/003). The exact file name can be found out by
running
sane-find-scanner which would print "libusb:001:003" in this case. While
setting permissions with e.g. "chmod a+rw /proc/bus/usb/001/003" seems
to work,
this change is not permanent. The permissions will be reset when the
scanner is
replugged or Linux is rebooted.
One solution to set permissions on-the-fly are the Linux hot-plug tools that
should come with any current distribution. SANE itsself comes with a
hotplug
script and related documentaion in the tools/hotplug/ directory. Please
refer to
the README in that directory for the details.
20 years
FC2-test3 install loader hangs if USB card reader is attached
by David Lerner
The install loader hangs after probing the USB bus if my flash card
reader is attached. The device has Vendor=058f ProdID=9360 Rev= 1.00.
Work around is to unplug the flash card reader or use the noprobe
install option.
I will try to enter this with bugzilla when it is up. It appears to be
down at this time.
20 years
kernel 2.6.5-1.347 and strange entries in kernel messages after latest selinux update
by RaXeT
I installed kernel 2.6.5-1.347 tonight and mind you I hve selinux=0 on
kernel boot and I'm now getting selinux activated anyway?
From messages:
May 2 20:05:35 raxet kernel: SELinux: Completing initialization.
May 2 20:05:35 raxet kernel: SELinux: Setting up existing superblocks.
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type
selinuxfs), uses genfs_contexts
May 2 20:05:35 raxet kernel: SELinux: initialized (dev sda3, type
ext3), uses xattr
May 2 20:05:35 raxet kernel: SELinux: initialized (dev ram0, type
ext2), uses xattr
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type mqueue),
not configured for labeling
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type
hugetlbfs), not configured for labeling
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type devpts),
uses transition SIDs
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type
eventpollfs), uses genfs_contexts
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type pipefs),
uses task SIDs
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type tmpfs),
uses transition SIDs
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type futexfs),
uses genfs_contexts
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type sockfs),
uses task SIDs
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type proc),
uses genfs_contexts
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type bdev),
uses genfs_contexts
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type rootfs),
uses genfs_contexts
May 2 20:05:35 raxet kernel: SELinux: initialized (dev , type sysfs),
uses genfs_contexts
May 2 20:05:35 raxet kernel: ieee1394: sbp2: Logged into SBP-2 device
May 2 20:05:35 raxet kernel: Vendor: LITE-ON Model:
LTR-48125W Rev: VS06
May 2 20:05:35 raxet kernel: Type:
CD-ROM ANSI SCSI revision: 02
May 2 20:05:35 raxet kernel: audit(1083528291.284:0): avc: denied {
getattr } for pid=1 exe=/sbin/init path=/dev/initctl dev=sda3 ino=65569
scontext=system_u:system_r:kernel_t tcontext=system_u:object_r:file_t
tclass=fifo_file
May 2 20:05:35 raxet kernel: audit(1083528291.284:0): avc: denied {
read write } for pid=1 exe=/sbin/init name=initctl dev=sda3 ino=65569
scontext=system_u:system_r:kernel_t tcontext=system_u:object_r:file_t
tclass=fifo_file
May 2 20:05:35 raxet kernel: audit(1083528292.497:0): avc: denied {
syslog_console } for pid=672 exe=/bin/dmesg
scontext=system_u:system_r:kernel_t tcontext=system_u:system_r:kernel_t
tclass=system
May 2 20:05:35 raxet kernel: audit(1083528292.771:0): avc: denied {
search } for pid=677 exe=/sbin/sysctl name=net dev= ino=-268435354
scontext=system_u:system_r:kernel_t
tcontext=system_u:object_r:sysctl_net_t tclass=dir
May 2 20:05:31 raxet sysctl: kernel.sysrq = 0
May 2 20:05:35 raxet kernel: audit(1083528292.771:0): avc: denied {
write } for pid=677 exe=/sbin/sysctl name=ip_forward dev=
ino=-268435331 scontext=system_u:system_r:kernel_t
tcontext=system_u:object_r:sysctl_net_t tclass=file
May 2 20:05:31 raxet sysctl: kernel.core_uses_pid = 1
May 2 20:05:35 raxet kernel: audit(1083528292.771:0): avc: denied {
getattr } for pid=677 exe=/sbin/sysctl
path=/proc/sys/net/ipv4/ip_forward dev= ino=-268435331
scontext=system_u:system_r:kernel_t
tcontext=system_u:object_r:sysctl_net_t tclass=file
May 2 20:05:31 raxet network: Setting network parameters: succeeded
What's with this?
RaXeT
20 years
Rebuilding kernel-source for NVIDIA drivers help!
by fedora
I'm trying to get NVIDIA drivers to work with FC2T3's kernel-2.6.5-1.327
-- no luck. Maybe you guys can tell me what am I doing wrong here, it
will benefit a lot of people I presume.
Here is what I did
I downloaded kernel-2.6.5-1.327.src.rpm and
NVIDIA-Linux-x86-1.0-5341-pkg1.run
1. rpm -i kernel-2.6.5-1.327.src.rpm
2. commented out "Patch200: linux-2.6.5-nostack.patch" and "%patch200
-p1" from spec file (in /usr/src/redhat/SPECS)
3. rebuilt kernel with: rpmbuild -bb
/usr/src/redhat/SPECS/kernel-2.6.spec (It made the package:
kernel-2.6.5-1.327.root.i386.rpm) <-- why the suffix?
4. installed new kernel-source: rpm -ivh /usr/src/redhat/RPMS/i386/
-it placed linux-2.6.5-1.327.root into /usr/src/
5. did sh NVIDIA-Linux-x86-1.0-5341-pkg1.run --add-this-kernel (built
custom package)
6. tried running custom package: sh
NVIDIA-Linux-x86-1.0-5341-pkg1.custom.run, got error saying cannot find
kernel-sources
7. specified kernel sources with sh
NVIDIA-Linux-x86-1.0-5341-pkg1.custom.run
--kernel-source-path=/usr/src/linux-2.6.5-1.327.root
8. received error saying NVIDIA kernel was built with different
kernel-source
I installed and removed kernel-sources back and forth (original
2.6.5-1.327 and rebuilt one). Tried a few combinations with the
installer and no luck. Minion.de patches don't work either, neither do
sh.nu packages.
Cheers, and TIA.
20 years
Re: desktop switching tool still buggy
by Rory Gleeson
In my case, this workaround doesn't do the trick with today's updates. I
can switch permanently to KDE and Xfce, but not permanetly to Gnome.
So, while I can now activate switchdesk for the first time after today's
updates, getting it to stick to a Gnome default continues to be
difficult.
As a temporary solution, would erasing this file knock me back to Gnome
or cause damage?
remove /root/.Xclients
Rory
>See bugzilla # 121840. Version 4.0.3-1 fixes the basic problem, but
>if you have selected KDE and then want to select Gnome from KDE, the
>gui already shows Gnome as default, but to make it really change to
>Gnome, you need to first select KDE and then select Gnome. It will
>then switch to Gnome. The bug report listed above has this
>information.
20 years
Re: desktop switching tool still buggy
by Rory Gleeson
In my case, this workaround doesn't do the trick with today's updates. I
can switch permanently to KDE and Xfce, but not permanetly to Gnome.
So, while I can now activate switchdesk for the first time after today's
updates, getting it to stick to a Gnome default continues to be
difficult.
As a temporary solution, would erasing this file knock me back to Gnome
or cause damage?
remove /root/.Xclients
>See bugzilla # 121840. Version 4.0.3-1 fixes the basic problem, but
>if you have selected KDE and then want to select Gnome from KDE, the
>gui already shows Gnome as default, but to make it really change to
>Gnome, you need to first select KDE and then select Gnome. It will
>then switch to Gnome. The bug report listed above has this
>information.
20 years
Couple of nits from FC2T3 install
by Willem Riede
I have custom NFS-installed FC2T3 without any problem on my dual PIII
test PC (Supermicro P6DBS, Adaptec 7895 SCSI adapter, SCSI disks).
When booting it for the first time, I encountered the following:
1) Console mouse services failed to start with "no mouse configured".
However, anaconda recognized my mouse just fine, and it works in X.
This is a PS2 wheel mouse behind an ATEN KVM. FC1 and before that RH8,9
set up the mouse for the console just fine.
2) I was asked twice what resolution display I wanted. Initially also
asked to confirm graphics card + monitor, then, in the middle of
firstboot, just the resolution + color depth.
3) In spite of running with selinux disabled, there are still log entries
about it -- why? Here is what I have, first set from boot:
May 2 09:52:01 fallguy kernel: Security Scaffold v1.0.0 initialized
May 2 09:52:01 fallguy kernel: SELinux: Initializing.
May 2 09:52:01 fallguy kernel: SELinux: Starting in permissive mode
May 2 09:52:01 fallguy kernel: There is already a security framework initialized, register_security failed.
May 2 09:52:02 fallguy kernel: Failure registering capabilities with the kernel
May 2 09:52:02 fallguy kernel: selinux_register_security: Registering secondary module capability
Second set when I ran up2date (from the GUI):
May 2 10:59:41 fallguy userhelper[5272]: running '/usr/sbin/up2date' with root privileges on behalf of 'wriede'
May 2 11:02:01 fallguy kernel: security_context_to_sid: called before initial load_policy on unknown context system_u:object_r:default_t
May 2 11:02:01 fallguy kernel: security_context_to_sid: called before initial load_policy on unknown context system_u:object_r:root_t
May 2 11:02:01 fallguy kernel: security_context_to_sid: called before initial load_policy on unknown context system_u:object_r:home_root_t
May 2 11:02:01 fallguy kernel: security_context_to_sid: called before initial load_policy on unknown context system_u:object_r:home_root_t
May 2 11:02:01 fallguy kernel: security_context_to_sid: called before initial load_policy on unknown context system_u:object_r:user_home_dir_t
[ and many, many lines more like it ].
4) I chose not to install Mozilla (deselected graphical internet) but still
have the web browser task bar icon (which fails if clicked, obviously).
All in all much better than T1 or T2, where I got totally bogged down
by selinux issues.
Keep up the good work! Willem Riede.
20 years
Error in update policy-sources-1.11.2-21
by Efthym
Hi all,
while doing todays updates i got the following error
[root@Purgatory incoming]# yum update
Gathering header information file(s) from server(s)
Server: Fedora Core 1.92 - Development Tree
Finding updated packages
Downloading needed headers
Resolving dependencies
Dependencies resolved
I will do the following:
[update: policy-sources 1.11.2-21.noarch]
[update: kudzu 1.1.58-1.i386]
[update: policy 1.11.2-21.noarch]
[update: system-config-bind 2.0.2-5.noarch]
[update: switchdesk 4.0.3-1.noarch]
[update: ltrace 0.3.32-2.i386]
[update: gnome-applets 1:2.6.0-4.i386]
[update: kudzu-devel 1.1.58-1.i386]
[update: SysVinit 2.85-25.i386]
[update: screen 4.0.2-2.i386]
[update: switchdesk-gui 4.0.3-1.noarch]
[update: gtkam-gimp 0.1.11-2.i386]
[update: gtkam 0.1.11-2.i386]
[update: xfce4-panel 4.0.5-2.i386]
Is this ok [y/N]: y
Downloading Packages
<snip>
policy 100 % done 3/28
policy-sources 100 % done 4/28
make: Entering directory `/etc/security/selinux/src/policy'
mkdir -p /etc/security/selinux
/usr/bin/checkpolicy -o /etc/security/selinux/policy.17 policy.conf
/usr/bin/checkpolicy: loading policy configuration from policy.conf
domains/program/acct.te:13:ERROR 'syntax error' at token 'type' on line
68236:
type acct_t, domain, privlog ;
#line 13
/usr/bin/checkpolicy: error(s) encountered while parsing configuration
make: *** [/etc/security/selinux/policy.17] Error 1
make: Leaving directory `/etc/security/selinux/src/policy'
After this I went to init 1 and run fixfiles relabel. No errors came up.
Nothing in messages either. I'm running with enforcing=1.
Maybe its just me (its been a while since a fresh install).
--
Opera 7.50beta1 on FedoraCore2_Test3
20 years
