No video with old motherboard - Biostar M6VLR - Trident chipset
by Javier Perez
Hi
I cannot get video with F19 on a very old home server.
The server is based on a Biostar M6VLR motherbaord. It has integrated video
with a "Trident Blade 3D Core"
I have not been able to get a good graphical desktop since several releases
ago.
It is not that important given that it is working ok as a NAS and I am
administering it via text mode.
Nevertheless, philosophically I feel bad not being able to start a graphic
session.
What logs should I post that might help you out? I guess dmesg, Xorg.0.log,
what else??
Thax
--
------------------------------
/\_/\
|O O| pepebuho(a)gmail.com
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
10 years, 8 months
fedora 19 + 3.10 + amd catalyst 13.8 broken
by Nate Pearlstein
I realize that it is bad form to complain about proprietary software in
this forum but since the 3.10 kernel and the catalyst 13.8 beta fglrx I
have a system that will not get to the graphical login prompt. I see
others complaining about what is likely the same. It isn't clear to me
who to pass this information to at amd or rpmfusion. gnome-shell fails
with a segfault from libcogl
Of course gdm works fine with the open source radeon driver.
So, anyone know who to provide feedback to with respect to the amd
fglrx dirver and what information they might like?
--
Nate Pearlstein - npearl(a)sgi.com - Product Support Engineer
10 years, 8 months
Grub2 problems
by Frank McCormick
I have been having some minor problems with grub2 lately - grub
is installed in /dev/sda the only HD on this machine.
When the grub menu comes up after a boot/reboot I cannot select
certain items as the selection bar just skips by them. Usually
I can select them if I start at the bottom and then they will not
be skipped, but others will.
Another problem which may be related - if I try to edit one of the items
before booting, a get double characters ( like ssiinnggllee). Then it
seems grub ignores what I have typed in. If I add single to the kernel
line it boots like I didn't type in anything.
This is a relatively new Fedora 19 installation, with a USB keyboard.
I updated the machine's BIOS in case there was a problem with it but
nothing changed.
Does anyone have any ideas ?
Thanks
10 years, 8 months
Re: The state of blu-ray burning in linux is terrible
by Thomas Schmitt
Hi,
sorry for breaking the thread. I was not subscribed up to now
and did not yet find an archive that exposes message ids.
--------------------------------------------------------------
It is not that bad with Blu-ray. At least with the backends.
(I am the developer of libburn and use BD-R and BD-RE media daily.)
But wodim (or "cdrecord") out of cdrkit should really be used
only for CD.
The slowliness of BD media comes from their Defect Management
which checkreads the written blocks while they are still present
in the drive's buffer. In case of poor read quality the blocks
get written again or redirected to the Spare Area where the data
get stored in replacement blocks.
This checkreading reduces write speed to at most half of the
nominal speed of drive and BD medium.
BD-R do Defect Management by default if they are formatted.
BD-RE can only be used formatted and do Defect Management by default.
--------------------------------------------------------------
Original cdrecord out of cdrtools was already discussed in the this
thread. To my knowledge it is fast with BD-R, because it does not
format them. It is not fast with BD-RE, because it uses SCSI command
WRITE(10) which does not allow to override the slow Defect Management.
--------------------------------------------------------------
growisofs out of dvd+rw-tools has a little bug with BD-R.
https://bugzilla.redhat.com/show_bug.cgi?id=858029
https://bugzilla.redhat.com/show_bug.cgi?id=868527
It is supposed to be fixed in
dvd+rw-tools-7.1-13.fc19
The tiny patch is shown in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016
Workaround is to explicitely format the BD-R before use by
dvd+rw-format /dev/sr0
or to use option
-use-the-force-luke=spare:none
when giving an unformatted BD-R to growisofs.
growisofs formats BD-R by default and then uses slow Defect
Management. This can be prevented by option
-use-the-force-luke=spare:none
growisofs has no means to prevent Defect Management on BD-RE media.
--------------------------------------------------------------
My own programs, libburn based cdrskin and xorriso, do not format
BD-R by default. So they are as fast as with cdrecord.
Other than with cdrecord it is possible to format BD-R on request
cdrskin -v dev=/dev/sr0 blank=format_if_needed
xorriso -outdev /dev/sr0 -format as_needed
which makes them capable of slow Defect Management.
Other than growisofs and cdrecord, cdrskin and xorriso offer the
opportunity to disable Defect Management on formatted BD-R and
on BD-RE
cdrskin stream_recording=on ...cdrecord-like-burn-options...
xorriso -stream_recording on ...xorriso-burn-commands...
This is especially helpful with 2x BD-RE, which elsewise need
an awfully long time to write their capacity of 22.5 GiB.
Have a nice day :)
Thomas
10 years, 8 months
Cannot install boost-static...
by Georgios Petasis
Hi all,
I am trying to install boost-static, but I am getting an error:
> yum install boost-static.i686
Loaded plugins: auto-update-debuginfo, langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package boost-static.i686 0:1.53.0-6.fc19 will be installed
--> Processing Dependency: boost-devel = 1.53.0-6.fc19 for package:
boost-static-1.53.0-6.fc19.i686
--> Finished Dependency Resolution
Error: Package: boost-static-1.53.0-6.fc19.i686 (fedora)
Requires: boost-devel = 1.53.0-6.fc19
Installed: boost-devel-1.53.0-8.fc19.i686 (installed)
boost-devel = 1.53.0-8.fc19
Available: boost-devel-1.53.0-6.fc19.i686 (fedora)
boost-devel = 1.53.0-6.fc19
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
How can I fix this?
George
10 years, 8 months
How to update F19 XFCE iso image with fixed Glibc and Midori browser already on updates repo?
by Fernando Cassia
I'm running F19 XFCE 32 bit on an Atom netbook booted from a pen drive
with the LiveCD ISO image.
The problem with F19 that didn't exist with F18 XFCE is that Midori
crashes, randomly.
Basically it can either crash on the first page loaded, or sometimes
last up to 10 minutes of usage with several tabs, then suddenly crash.
I remember reading it was all about a bug in glibc.
However, running 'yum update glibc' 'yum update midori' after booting
the LiveCD (either one or both) ultimately leads to an unstable system
that crashes shortly after (the whole system crashes, perhaps due to
having different glibc versions, some in use and new apps using the
new one? I'm speculating on this).
Whatever the case, I'd like to have a F19 XFCE 32-bit image that I can
boot on this netbook from the pen drive and safely use.
If anyeone feels like walking me through the steps required to update
both glibc and Midori in an existing ISO image, I'm all ears... (I
tried Googling but didn't found a human-friendly step by step guide or
tool like "updateiso fedora19-xfce-whatever.iso fixedmidori.rpm
fixedglibc.rpm")
What to do?
TIA...
FC
10 years, 8 months
Generate CRL for NSS Self Signed CA
by William
Hi,
I am currently experimenting with a self signed CA using NSS at the
moment.
I would like to be able to create certificates, sign them with the CA,
and be able to revoke them via some CRL mechanism.
At the moment, I can achieve the first two steps, but the method of
revoking a certificate from an NSS db, and then creating a CRL from that
is eluding me. I have tried to research this quite a bit, and reading of
various man pages are not sheding light upon this situation for me.
Does anyone have any tips or knowledge about what to do to achieve this?
--
Sincerely,
William Brown
pgp.mit.edu
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x3C0AC6DAB2F928A2
10 years, 8 months
Xastir
by jarmo
Hello list
Anyone else using XASTIR, aprs hamradio tracking program.
I have version 2.0.0 rpm. Is there newer one. I see official version
which is 2.0.4.
If package manager see this, is it big trouble to make 2.0.4 available.
I'd like to use rpm, not compile from source. Have done it earlier, but
mix rpm and source messes system, hi.
Jarmo
10 years, 8 months
Do I need avahi?
by Timothy Murphy
I recently noticed that I have been getting warnings
avahi-daemon[5884]: dbus-protocol.c:
Too many objects for client ':1.15', client request failed.
on my server.
I must admit I didn't know I was running avahi on the server.
I looked at a couple of avahi howtos,
and it seemed that for almost any usage other packages are required,
in particular nss-mdns .
If this is in fact required by avahi, it seems surprising
that it is not automatically installed at the same time.
(None of the examples of avahi usage actually worked on my system.)
But my real query is whether avahi (or zeroconf)
could actually offer me anything useful.
I'm running dhcpd on the server,
and I'm not looking for information about printers
or other users on my home network.
Also, is there any way of discovering who "client 1.15" is?
And is anything likely to go wrong if I simply "service avahi-daemon stop"?
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
School of Mathematics, Trinity College, Dublin 2, Ireland
10 years, 8 months
Gnome classic working in F19?
by "Paul-Erik Törrönen"
Just want to check first if I am the only one having this problem with an
upgraded F19 setup.
Some background:
Upgraded the system from F18 (and previously from 17-16-15) with fedup
--network. Before the upgrade I was running Gnome fine in the classical
style (dropdown app menu, no hotspots, workspace grid on lower bar etc.).
After the upgrade logged on with Gnome Classic selected -> worked fairly
ok, I have a grey top and bottom bar. Logged out and in again in order to
get some additional settings (the workspace for both dual displays). After
the login (making sure that I still have the Gnome classic selected) the
top and bottom bars are not the same.
Specifically the bottom bar (where the running apps should be displayed as
well as the workspace app) is missing altogether and the top bar is now
the new Gnome-styled, ie. has the hotspot and no app-menu at all.
This is reproducable, if I log out from this state, select the normal
gnome session, then I (again) get the same new Gnome desktop as described
above, and after an additional logout + login with the Gnome Classic
selected, then I end back in the actual classic for that particular
session.
So it seems that the mode selection is not really working, and neither is
the selection remembered correctly.
Does this sound familiar to anyone?
Poltsi
--
Paul-Erik Törrönen "When science and the Bible differ,
poltsi(a)777-team.org science has obviously misinterpreted
+358 40 703 1231 its data"
http://poltsi.fi/ Henry Morris, father of 'modern creationism'
10 years, 8 months