Fedora 20 installation on Lenovo N500 fails
by Kevin Wilson
Hello all,
I tried to install Fedora 20 on Lenovo N500 laptop (x86_64) from a DVD.
I verified the DVD media and also I had installed a desktop today with this
DVD.
When I try to install it on Lenovo N500 laptop (x86_64) it fails - it reboots.
I tried several times.
I also tried in text mode ("linux text") and again it fails.
Any ideas ?
Regards,
Kevin
10 years, 5 months
securing remote/distributed boxes
by bruce
Hi.
Continuing a thread I've been posting on...
I've got a project where there will be a number of client boxes across
the net. The boxes will run a base fedora/centos, and be used as
"compute" nodes if you will.
The boxes will need to connect back to the master server(s) to
exchange information.
The masterservice sends information out using a queing process
(gearman/etc) and the child/client box gets the data, processes it,
returns the data.
So, from the child/clientside, the client box needs to be able to have
remote access to the master queue, via the tunnelling/port process.
This (at least to me) means I've got to have ssh running/ports open,
along with the ability to have pub/private keys so i can
programatically access/shove data across the ssh tunnels.
The boxes need to be locked down/secure as possible.
Other than ssh/internet access, and a few local apps/processes, most
of the other services can be shut down in order to make the box as
secure as possible.
The boxes will not have "users" accessing the box.
Think of the box, as a node on a BOINC/SETI kind of system, where a
bunch of edgenode boxes are used to do computational processing.
Thoughts/comments are welcome.
Thanks
10 years, 5 months
trying to mount usb/hard drive
by bruce
Hi,
The drive from the 1st system is a 640G drive
The partition data from the system monitor app gives the following:
/dev/mapper/vg_dell45_lv_root /
/dev/mapper/vg_dell45_lv_apps /apps
/dev/mapper/vg_dell45_lv_backup /backup
/dev/sda1 /boot
/dev/mapper/vg_dell45_lv_home /home
When I pop the drive into a usb drive bay to examine/view the drive
from the 2nd system, I only get the 340M slice of the drive.
when I do a "fdisk -l" on the drives in the 2nd system, it sees the "drive",
Disk /dev/sdc: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x28000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sdc2 64 77826 624618496 8e Linux LVM
So the question is what do I have to "enter/type" at the cmdline to
actually mount the given partition "/apps, /home" of the 640G drive to
be able to access the underlying data??
thanks
10 years, 5 months
f20 install :: partitioning crazy bugs!!!
by Adrian Sevcenco
Hi! I am trying to install an f20 (because fedup-ing from f17 is not
working because of plymonth!!! (another moronic idea!! : both plymoth
and basing the ditro upgrading process on plymoth!!!))
the problems are:
1. it request me to have a stage1 bootloader partition!! i dont have
uefi enabled and i dont want one (both uefi and bootloader)
2. it requires for me to have a swap!!! I DO NOT WANT SWAP! (well i can
have it on an usb stick and remove later but this requirement is moronic
(because i have no choice!))
so .. anyone have any idea how can i solve the first problem?
Thanks!
Adrian
10 years, 5 months
Oopses from wireless device in F19
by Paolo Galtieri
I just recently installed F19 on a new Dell Inspiron R15 7537 and since
then I've been getting kernel oopses from the wireless device. What's
interesting :-( is that right before the oops if I do
cat /proc/sys/kernel/tainted
it returns 0. Right after the oops it returns 512.
I have no extra kernel modules installed. So I don't understand why it
suddenly shows my kernel as tainted. This oops happens at least once per
day, and sometimes more. The only way to get the wireless working is to
reboot. Also the network-manager applet still shows me as connected even
though I can't ping out to the internet. If I try to disconnect the
wireless and retry it never reconnects until I reboot the laptop.
Anyone else seen this behavior?
Output of lspci:
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated
Graphics Controller (rev 09)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller
(rev 09)
00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0
(rev 04)
00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller
(rev 04)
00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1
(rev e4)
00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3
(rev e4)
00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4
(rev e4)
00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1
[AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
Any assistance is appreciated.
I submitted a bug via the abort applet, but I can't find the number.
Paolo
10 years, 5 months
FedUp 18 -> 19 Orphans
by Kevin H. Hobbs
I just updated from Fedora 18 to 19 with fedup.
After the update I have many orphaned packages :
# package-cleanup --orphans | wc -l
635
When I examine them I see things like fedora-release, zlib, and such.
They mostly exist alongside their identical fedora 19 versions :
# package-cleanup --orphans | grep libogg
libogg-1.3.0-5.fc18.x86_64
# yum list libogg
Loaded plugins: auto-update-debuginfo, verify
Installed Packages
libogg.x86_64 2:1.3.0-5.fc18 installed
libogg.i686 2:1.3.0-5.fc19 installed
libogg.x86_64 2:1.3.0-5.fc19 installed
Any idea what's going on?
10 years, 5 months
f20 - yum locally rebuilding deltas is so slow
by Robert Moskowitz
On my Asus 900.
I just started a yum update fire* libre* that took next ot no time to
download from my local repo, but took over 10 min to build the local
delta. Seems I am better of NOT having drpms available.
hmmm...
10 years, 5 months
f20 strange local repo behaviour
by Robert Moskowitz
when I edited the yum.repos.d files to point to my local repos, I got
the following error doing a yum update:
Error: Package: gnutls-utils-3.1.17-3.fc20.i686 (updates)
Requires: libopts.so.25
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
I have the same number of files locally that I am seeing on the mirrors,
so what gives? Is there perhaps a permission problem? I used rsync to
build my repo:
rsync -auv --delete --exclude=debug/
rsync://mirrors.kernel.org/fedora/updates/20/i386/
/var/flexshare/shares/repo/fedora/20/updates/i386
10 years, 5 months