NetworkManager
by jarmo
From various ditros have informed, that NM stopped autoconnecting
mobile broadband dingel dongels. Yes it is true. An what is mystery, it
it is still "broken".
Please, some of you NM guys reading this list, fix it. There is lot's of
reports done. So, is it purpose, or Bug? It has worked before 0.9
series.
Jarmo
11 years, 7 months
Howto resolve crash address into function name / line number?
by Clemens Eisserer
Hi,
I see usb_modeswitch frequently crashing with a segfault, and a message
like:
Oct 31 19:38:28 localhost kernel: [ 33.953670] usb_modeswitch_[1373]:
segfault at 7fffd64bfbe4 ip 0000003000874b06 sp 00007fffd64bfbd0 error 6 in
libc-2.15.so[3000800000+1ac000]
Is there any way to trace back 7fffd64bfbe4 to the function name / line
number?
Thank you in advance, Clemens
11 years, 7 months
Setting up JBoss for Eclipse
by Christopher Svanefalk
I recently migrated from Netbeans and GlassFish to Eclipse and JBoss. I
have installed the eclipse-jboss tools, and the server runtime is set up
properly (afaik at least).
The problem I have is that whenever I try to start JBoss from Eclipse, I
get this:
20:37:23,853 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
20:37:24,136 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
20:37:24,194 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
"Brontes" starting
20:37:24,306 ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start
service jboss.deployment-mount-provider:
org.jboss.msc.service.StartException in service
jboss.deployment-mount-provider: JBAS015843: Failed to create temp file
provider
at
org.jboss.as.server.deployment.DeploymentMountProvider$Factory$ServerDeploymentRepositoryImpl.start(DeploymentMountProvider.java:111)
[jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc.jar:1.0.2.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc.jar:1.0.2.GA]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[rt.jar:1.7.0_09-icedtea]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[rt.jar:1.7.0_09-icedtea]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
I have googled this and tried all workarounds I could find, including (!!!)
giving jboss-as.service root priviliges (I know, it's a horrible idea).
Nothing helps. Could anyone help? It would be greatly appreciated.
Best,
Christopher Svanefalk
mob: +46762628251
skype: csvanefalk
11 years, 7 months
First f17 install -- on an ee701
by Robert Moskowitz
I have 1Gb of memory upgrade, so I have enough memory. My SSD is only
4Gb, but I have a 16GB SD card.
So the SSD is setup for /boot with 300Mb, swap with 1.6Gb and the rest
is /var. The SD is /
The challenge with the install is the small screen size. I complained
about this and submitted a bug on it with f14 (which was the only
install I have made on this ee701). Apparently the developers did not
feel it necessary to do anything about adjusting the dialog sizes to the
actual screen size. For the most part I was able to guess what keys to
hit for the buttons cut off below the bottom of the screen. I could not
see how to setup a LVM on the SD, so it is just and ext4 partition.
Also I could not go into customizing the packages for the install and
although I did provide my local repos so I grabbed all the updates right
off, I had to just go with the standard graphic desktop package install....
Next I will have to do the gnome 3 customizations. Though I MIGHT just
leave it for the defaults for a while, rather than all the customzations
I did for this f16 notebook a year ago. I actually would like to wait
for f18 for upgrading my main notebook; I kind of like skipping releases...
Anyway. so far so good.
11 years, 7 months
Change default stacksize
by Lester M Petrie
The default stacksize on my machine (Fedora 17, KDE) is apparently 8Mb. I
think that ridiculous. A long time ago I knew how to change it, but I have
forgotten what I knew, and it probably wouldn't work now anyway. So how do I
set the default stacksize (what a user gets if they don't specify anything)?
Thanks.
--
Lester M Petrie
865-574-5259
petrielmjr(a)ornl.gov
11 years, 7 months
home made (F17) systemd script not working F14
by Gary Stainburn
The following file is the one I created for my F 17 test bed system which
worked fine.
I've not put it onto my production F 14 system but it won't start.
Enable worked but the service didn't run on restart
I have no knowledge of systemd so I'm struggling here.
[root@lou system]# systemctl start faxgetty-ttyS0.service
Failed to get D-Bus connection: Failed to connect to
socket /org/freedesktop/systemd1/private: Connection refused
[root@lou system]# cat faxgetty-ttyS0.service
[Unit]
Description=FaxGetty Start Modem ttyS0
[Service]
Type=simple
User=root
Group=root
Restart=always
ExecStart=/usr/local/sbin/faxgetty /dev/ttyS0
RestartSec=30
[Install]
WantedBy=multi-user.target
[root@lou system]#
11 years, 7 months
Unable to Display English Characters
by Singapore Citizen Mr. Teo En Ming (Zhang Enming)
Hi,
I need help. I have just installed Fedora 17 from the DVD. I used text
mode installation and later converted to GUI mode using
yum groupinstall "X Window System" Desktop
and configuring systemd.
Please refer to the image below. The GUI cannot display English
characters. All I get are square boxes.
http://i.imgur.com/sKUrl.png
Thank you very much.
--
Yours sincerely,
Mr. Teo En Ming (Zhang Enming)
Singapore
11 years, 7 months
Dynamode PCI serial card into Fedora 17 system
by Gary Stainburn
My system already had one serial port, ttyS0 which is working.
I've installed a Dynamode 2-port serial card and the kernel sees the two
ports. This provides two ports is:
PCI Spec Revision 2 compliant
Compatible with 16C550 UART
and says that it supports Linux.
However, I can't use them. I've tried using both minicom and faxxaddmodem (I'm
setting up a Hylafax modem bank).
Can anyone suggest what I need to do please.
[root@stan2 ~]# dmesg|grep tty
[ 0.000000] console [tty0] enabled
[ 0.690683] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.711711] 00:04: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.712208] 0000:00:09.0: ttyS1 at I/O 0xec00 (irq = 17) is a XScale
[ 0.712602] 0000:00:09.0: ttyS2 at I/O 0xe880 (irq = 17) is a XScale
[root@stan2 ~]# lspci|grep -i serial
00:09.0 Serial controller: Device 4348:3253 (rev 10)
[root@stan2 ~]# setserial /dev/ttyS1
/dev/ttyS1, UART: undefined, Port: 0xec00, IRQ: 17
[root@stan2 ~]# ll /dev/ttyS*
crw-------. 1 uucp dialout 4, 64 Oct 31 14:33 /dev/ttyS0
crw-rw----. 1 root dialout 4, 65 Oct 31 14:34 /dev/ttyS1
crw-rw----. 1 root dialout 4, 66 Oct 31 14:34 /dev/ttyS2
crw-rw----. 1 root dialout 4, 67 Oct 31 2012 /dev/ttyS3
[root@stan2 ~]#
--
Gary Stainburn
Group I.T. Manager
Ringways Garages
http://www.ringways.co.uk
11 years, 7 months
upgraded faster SSD, slower reads
by Wolfgang S. Rupprecht
I just bought a fast Intel series 520 SSD (240 GB, 550 MBytes/sec) to
replace my slower series 320 SSD (120 GB, 250MBytes/sec). I was
expecting the speed when reading the ssd to jump from my current read
speeds of around 250 MBytes/sec to (hopefully) something at least twice
that speed. The specs say the 520 does 550 MBytes/sec for read and
almost that for write. To my surprise the series 520 was only ~130
MBytes/sec. This is observed under Fedora-17 using "dd if=/dev/sdb2
of=/dev/null bs=64k count=1000". The board is an older Asus M3A78T and
has been happily running the 320 at full rated speed for 1.5 years.
Intel series 320:
dd if=/dev/sda2 of=/dev/null bs=64K count=1000
1000+0 records in
1000+0 records out
65536000 bytes (66 MB) copied, 0.254144 s, 258 MB/s
Intel series 520:
dd if=/dev/sdb2 of=/dev/null bs=64K count=1000
1000+0 records in
1000+0 records out
65536000 bytes (66 MB) copied, 0.494915 s, 132 MB/s
These number stay relatively constant, no matter how many seconds of
transfer I do. Ditto for changing block size (bs=...) up to 1MByte. I
see these numbers for the 520 when I attach it on the same SATA
3Gbit/sec link as the 320 or if I attach it on a new SATA 6Gbit/sec
controller (Highpoint Rocket 620, a Marvel 88SE9125 PCIe SATA 6.0 Gb/s
controller). I do see it attach at 3 Gbit/sec on the old controller and
6 Gbit/sec on the new controller. (So it isn't going down to SATA-1
speeds as far as the printf's I can see indicate.)
Is the 520 defective? Ideas? The reviews of the 520 all show it
really truly doing > 500MBytes/sec. These suckers can really fly.
Just not for me...
Google searches show that some folks running MS software have had
similar problems and they managed to fix things by downgrading their
BIOS setting to use IDE settings for the SSD. Other hits mentioned
something about power management on the SATA being the culprit and IDE
drivers nailed the power on instead of letting it flap in the wind. Is
this something I can turn off from userland without recompiling the
kernel?
-wolfgang
--
g+: https://plus.google.com/114566345864337108516/about
11 years, 7 months
