What kernel has a built-in support for this wlan card?

2016-01-21 Thread M. Gelle 
Hello,

If there's no current kernel that supports this card, then what's the eta
for Fedora 23 with:

Network controller: Qualcomm Atheros Device 0042 (rev 30). It's the QCA9377
model I believe.
The reason I ask is because this Lenovo Laptop has the weird ideapad_laptop
module.

I even tried disabling the Secure Boot to no avail - rfkill couldn't enable
wlan. Otherwise drivers will not load due to the "required key kissing"
error.


dmidecode | grep 'System Information' -A8

System Information
Manufacturer: LENOVO
Product Name: 80QD
Version: Lenovo YOGA 700-14ISK
Serial Number: PF0EKTY1
UUID: 4F9FAF54-8C06-11E5-8FC7-507B9D6D7E08
Wake-up Type: Other
SKU Number: LENOVO_MT_80QD_BU_idea_FM_Lenovo YOGA 700-14ISK
Family: IDEAPAD



regards,
Mo
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: 4.3.3-300 DMAR: DMAR:[DMA Write] Request device [8a:06.1] fault addr fc26e000

2016-01-21 Thread jarmo 
Thu, 21 Jan 2016 18:21:01 +
Nate Pearlstein  kirjoitti:

> Seeing errors after upgrading from 4.2.8-300 to 4.3.3-300, I also see

I get similar...
 WARNING:  Kernel Errors Present
Buffer I/O error on dev dm-1, log ...:  102 Time(s)
Buffer I/O error on device dm-1,  ...:  390 Time(s)
EXT4-fs error (device dm-1): _ ...:  11 Time(s)
EXT4-fs warning (device dm-1): ext4_end_bio:329: I/O error -5 writing to in 
...:  204 Time(s)
WARNING: CPU: 0 PID: 415 at fs/buffer.c:1160 mar ...:  1 Time(s)
ata1.00: cmd 61/00:00:98:05:7c/08:00:09:00:00/40 tag 0 ncq 1048576 out#012  
   res 40/00:08:30:ed:6f/00:00:09:00:00/40 Emask 0x60 (host bus error) ...: 
 2 Time(s)
ata1.00: cmd 61/00:00:98:05:7c/08:00:09:00:00/40 tag 0 ncq 1048576 out#012  
   res 40/00:10:e0:de:ff/00:00:08:00:00/40 Emask 0x60 (host bus error) ...: 
 1 Time(s)
ata1.00: cmd 61/00:00:98:05:7c/08:00:09:00:00/40 tag 0 ncq 1048576 out#012  
   res 40/00:20:00:70:bc/00:00:09:00:00/40 Emask 0x60 (host bus error) ...: 
 2 Time(s)
ata1.00: cmd 61/00:00:98:05:7c/08:00:09:00:00/40 tag 0 ncq 1048576 out#012  
   res 40/00:20:10:93:55/00:00:04:00:00/40 Emask 0x60 (host bus error) ...: 
 1 Time(s)
ata1.00: cmd 61/00:00:98:05:7c/08:00:09:00:00/40 tag 0 ncq 1048576 out#012  
   res 40/00:20:d8:8c:58/00:00:05:00:00/40 Emask 0x60 (host bus error) ...: 
 1 Time(s)
ata1.00: cmd 61/00:00:98:05:7c/08:00:09:00:00/40 tag 0 ncq 1048576 out#012  
   res 40/00:60:90:a4:6c/00:00:0d:00:00/40 Emask 0x60 (host bus error) ...: 
 1 Time(s)
ata1.00: cmd 61/00:00:98:05:7c/08:00:09:00:00/40 tag 0 ncq 1048576 out#012  
   res 40/00:70:00:cf:6b/00:00:0d:00:00/40 Emask 0x60 (host bus error) ...: 
 1 Time(s)
ata1.00: cmd 61/00:00:98:05:7c/08:00:09:00:00/40 tag 0 ncq 1048576
out#012 res

I turned back into uname -a

Linux oh1mrr.ampr.org 4.2.8-300.fc23.i686+PAE #1 SMP Tue Dec 15
17:13:23 UTC 2015 i686 i686 i386 GNU/Linux
And no errors/warnings...

Jarmo

-- 
конец
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

screen/remote apps

2016-01-21 Thread bruce 
Hi.

I can locally run screen, and then run an app.

If I wanted to have a process where I remotely start/run an app on a
remote box (ssh) via screen, How is this accomplished? Can it be done?

Ie, I want the app on the remote instance/box to be running in a
screen process within a term. This would allow someone to login, fire
up the screen process for the screen id, and see the process in
action...

Thanks for any pointers..
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: driver install but not loaded

2016-01-21 Thread thibaut noah 
Kernel is 4.2.5, i thought despite what was advertised it was possible to
run the driver 4.0.4+ (since they said one just has to rebuild the open
source driver with new kernel).
Isn't that possible to download old kernel and load the driver with it? (i
have no idea how, just making a supposition).
Otherwise i will just have to see if the tech support team can update the
driver...
Thanks anyway

2016-01-22 1:00 GMT+01:00 Rick Stevens :

> On 01/21/2016 03:49 PM, Rick Stevens wrote:
>
>> On 01/21/2016 03:09 PM, thibaut noah wrote:
>>
>>> Thanks for the enlightment.
>>> I manage to get the driver from the modules.gz archive and i made a new
>>> initframs using dracut --add-drivers but modprobe still cannot find it,
>>> possible that the module will indeed not work :/
>>> The error is saying :
>>> could not insert 'rr272x_1x' : Exec format error
>>>
>>
>> The driver was built incorrectly for this version of the system. Just
>> why, I don't know. It did get put into the correct directory or
>> modprobe/insmod wouldn't find it at all.
>>
>> Did i miss something? the driver is a .ko file
>>>
>>
>> Just because it's a .ko file doesn't mean it's compatible with a 4.x
>> kernel. Odds are that it isn't. You should browse High Point's web
>> site and see if there IS a version of that driver that's 4.x compatible.
>>
>> Sorry I can't be of more help.
>>
>
> I just looked at High Point's website and they have driver source
> compatible with kernels up to 4.0.4. Dunno which kernel you're running.
> My F23 box is running 4.3.3-300, my F22 is running 4.2.8-200. They're
> both too new for that driver.
>
>
> 2016-01-21 18:53 GMT+01:00 Rick Stevens >> >:
>>>
>>> On 01/21/2016 04:02 AM, thibaut noah wrote:
>>>
>>> updating this, i did some testing on the sh file and i found
>>> where the
>>> issue is coming from.
>>> There is two for loops (at least two that concerns me) and the
>>> code
>>> inside is never executed.
>>> Condition is :
>>> for dir in [23].*;do
>>> [ -d $dir/kernel/fs ] || continue
>>>
>>> I'm a bit lost here, what is this 23 number? it cannot be fedora
>>> number
>>> as this driver is the open source version of the fedora 17
>>> driver.
>>> Pretty sure if i modify the condition with a correct one
>>> everything
>>> should work properly
>>>
>>>
>>> F17? Well, that's probably the issue. What you're seeing is an
>>> attempt
>>> to walk down the various /lib/modules/2.* and /lib/modules/3.* trees
>>> to install the driver. If you're on F22 or F23, you probably don't
>>> HAVE
>>> 2.* or 3.* kernel trees. You have 4.x kernel trees.
>>>
>>> You could try changing that line from:
>>>
>>>  for dir in [23].*; do
>>>
>>> To:
>>>
>>>  for dir in [234].*; do
>>>
>>> That would include the 4.x kernel trees. I don't know if the
>>> module will
>>> work, though as it seems to be written for quite old kernels. YMMV
>>>
>>> 2016-01-21 12:21 GMT+01:00 thibaut noah >> 
>>> >> >>>:
>>>
>>>
>>>  Hello guys, got this weird error trying to install my raid
>>> driver :
>>>
>>>  Start to install the driver rr272x_1x.ko of rr272x_1x.
>>>  Finish installing the kernel module rr272x_1x.ko.
>>>  Loading rr272x_1x driver module rr272x_1x
>>>  modprobe: FATAL: Module rr272x_1x not found.
>>>
>>>  Checked with lsmod driver does not appear tough the
>>> installation is
>>>  finished (checked the sh file, modprobe is running at the
>>> end).
>>>  After a little read of the sh file i can confirm that the
>>> driver is
>>>  in /etc/rc.modules (it appears to be with sd_mod and that's
>>> all).
>>>  chmod on rc.modules in the sh file is successfull (chmod
>>> 755).
>>>  The failing part seems to be this :
>>>
>>>  elif [ "${MODULE}" = "rr272x_1x" -o "${MODULE}" =
>>> "rr274x_3x" -o
>>>"${MODULE}" = "rr276x" -o "${MODULE}" = "rr278x" ] ; then
>>>  ( cd /lib/modules/
>>>  for dir in [23].*; do
>>>  [ -d $dir/kernel/fs ] || continue
>>>  if [ -f /boot/initrd-$dir.img ]; then
>>>  mv /boot/initrd-$dir.img /boot/initrd-$dir.img.bak
>>>  # do not include mvsas in initrd, as the udev and so will
>>> load the
>>>  driver
>>>  mkinitrd --builtin=mvsas /boot/initrd-$dir.img $dir
>>>  elif [ -f /boot/initramfs-$dir.img ]; then
>>>  mv /boot/initramfs-$dir.img /boot/initramfs-$dir.img.bak
>>>  # do not include mvsas in initramfs, as the udev and so
>>> will load
>>>  the driver
>>>  dra

Re: driver install but not loaded

2016-01-21 Thread Rick Stevens 

On 01/21/2016 03:49 PM, Rick Stevens wrote:

On 01/21/2016 03:09 PM, thibaut noah wrote:

Thanks for the enlightment.
I manage to get the driver from the modules.gz archive and i made a new
initframs using dracut --add-drivers but modprobe still cannot find it,
possible that the module will indeed not work :/
The error is saying :
could not insert 'rr272x_1x' : Exec format error


The driver was built incorrectly for this version of the system. Just
why, I don't know. It did get put into the correct directory or
modprobe/insmod wouldn't find it at all.


Did i miss something? the driver is a .ko file


Just because it's a .ko file doesn't mean it's compatible with a 4.x
kernel. Odds are that it isn't. You should browse High Point's web
site and see if there IS a version of that driver that's 4.x compatible.

Sorry I can't be of more help.


I just looked at High Point's website and they have driver source 
compatible with kernels up to 4.0.4. Dunno which kernel you're running.

My F23 box is running 4.3.3-300, my F22 is running 4.2.8-200. They're
both too new for that driver.


2016-01-21 18:53 GMT+01:00 Rick Stevens mailto:ri...@alldigital.com>>:

On 01/21/2016 04:02 AM, thibaut noah wrote:

updating this, i did some testing on the sh file and i found
where the
issue is coming from.
There is two for loops (at least two that concerns me) and the
code
inside is never executed.
Condition is :
for dir in [23].*;do
[ -d $dir/kernel/fs ] || continue

I'm a bit lost here, what is this 23 number? it cannot be fedora
number
as this driver is the open source version of the fedora 17
driver.
Pretty sure if i modify the condition with a correct one
everything
should work properly


F17? Well, that's probably the issue. What you're seeing is an
attempt
to walk down the various /lib/modules/2.* and /lib/modules/3.* trees
to install the driver. If you're on F22 or F23, you probably don't
HAVE
2.* or 3.* kernel trees. You have 4.x kernel trees.

You could try changing that line from:

 for dir in [23].*; do

To:

 for dir in [234].*; do

That would include the 4.x kernel trees. I don't know if the
module will
work, though as it seems to be written for quite old kernels. YMMV

2016-01-21 12:21 GMT+01:00 thibaut noah mailto:thibaut.n...@gmail.com>
>>:


 Hello guys, got this weird error trying to install my raid
driver :

 Start to install the driver rr272x_1x.ko of rr272x_1x.
 Finish installing the kernel module rr272x_1x.ko.
 Loading rr272x_1x driver module rr272x_1x
 modprobe: FATAL: Module rr272x_1x not found.

 Checked with lsmod driver does not appear tough the
installation is
 finished (checked the sh file, modprobe is running at the
end).
 After a little read of the sh file i can confirm that the
driver is
 in /etc/rc.modules (it appears to be with sd_mod and that's
all).
 chmod on rc.modules in the sh file is successfull (chmod
755).
 The failing part seems to be this :

 elif [ "${MODULE}" = "rr272x_1x" -o "${MODULE}" =
"rr274x_3x" -o
   "${MODULE}" = "rr276x" -o "${MODULE}" = "rr278x" ] ; then
 ( cd /lib/modules/
 for dir in [23].*; do
 [ -d $dir/kernel/fs ] || continue
 if [ -f /boot/initrd-$dir.img ]; then
 mv /boot/initrd-$dir.img /boot/initrd-$dir.img.bak
 # do not include mvsas in initrd, as the udev and so will
load the
 driver
 mkinitrd --builtin=mvsas /boot/initrd-$dir.img $dir
 elif [ -f /boot/initramfs-$dir.img ]; then
 mv /boot/initramfs-$dir.img /boot/initramfs-$dir.img.bak
 # do not include mvsas in initramfs, as the udev and so
will load
 the driver
 dracut /boot/initramfs-$dir.img $dir
 fi
 done

 Can someone give me a hint on how to do what needs to be
done? I'm
 not familiar with drivers on unix systems so i'm a bit
lost, full sh
 file is attached if needed, thanks.


--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-Polygon: A dead parrot (With apologies to John Cleese)  -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mai

Re: driver install but not loaded

2016-01-21 Thread Rick Stevens 

On 01/21/2016 03:09 PM, thibaut noah wrote:

Thanks for the enlightment.
I manage to get the driver from the modules.gz archive and i made a new
initframs using dracut --add-drivers but modprobe still cannot find it,
possible that the module will indeed not work :/
The error is saying :
could not insert 'rr272x_1x' : Exec format error


The driver was built incorrectly for this version of the system. Just
why, I don't know. It did get put into the correct directory or
modprobe/insmod wouldn't find it at all.


Did i miss something? the driver is a .ko file


Just because it's a .ko file doesn't mean it's compatible with a 4.x
kernel. Odds are that it isn't. You should browse High Point's web
site and see if there IS a version of that driver that's 4.x compatible.

Sorry I can't be of more help.



2016-01-21 18:53 GMT+01:00 Rick Stevens mailto:ri...@alldigital.com>>:

On 01/21/2016 04:02 AM, thibaut noah wrote:

updating this, i did some testing on the sh file and i found
where the
issue is coming from.
There is two for loops (at least two that concerns me) and the code
inside is never executed.
Condition is :
for dir in [23].*;do
[ -d $dir/kernel/fs ] || continue

I'm a bit lost here, what is this 23 number? it cannot be fedora
number
as this driver is the open source version of the fedora 17 driver.
Pretty sure if i modify the condition with a correct one everything
should work properly


F17? Well, that's probably the issue. What you're seeing is an attempt
to walk down the various /lib/modules/2.* and /lib/modules/3.* trees
to install the driver. If you're on F22 or F23, you probably don't HAVE
2.* or 3.* kernel trees. You have 4.x kernel trees.

You could try changing that line from:

 for dir in [23].*; do

To:

 for dir in [234].*; do

That would include the 4.x kernel trees. I don't know if the module will
work, though as it seems to be written for quite old kernels. YMMV

2016-01-21 12:21 GMT+01:00 thibaut noah mailto:thibaut.n...@gmail.com>
>>:


 Hello guys, got this weird error trying to install my raid
driver :

 Start to install the driver rr272x_1x.ko of rr272x_1x.
 Finish installing the kernel module rr272x_1x.ko.
 Loading rr272x_1x driver module rr272x_1x
 modprobe: FATAL: Module rr272x_1x not found.

 Checked with lsmod driver does not appear tough the
installation is
 finished (checked the sh file, modprobe is running at the end).
 After a little read of the sh file i can confirm that the
driver is
 in /etc/rc.modules (it appears to be with sd_mod and that's
all).
 chmod on rc.modules in the sh file is successfull (chmod 755).
 The failing part seems to be this :

 elif [ "${MODULE}" = "rr272x_1x" -o "${MODULE}" =
"rr274x_3x" -o
   "${MODULE}" = "rr276x" -o "${MODULE}" = "rr278x" ] ; then
 ( cd /lib/modules/
 for dir in [23].*; do
 [ -d $dir/kernel/fs ] || continue
 if [ -f /boot/initrd-$dir.img ]; then
 mv /boot/initrd-$dir.img /boot/initrd-$dir.img.bak
 # do not include mvsas in initrd, as the udev and so will
load the
 driver
 mkinitrd --builtin=mvsas /boot/initrd-$dir.img $dir
 elif [ -f /boot/initramfs-$dir.img ]; then
 mv /boot/initramfs-$dir.img /boot/initramfs-$dir.img.bak
 # do not include mvsas in initramfs, as the udev and so
will load
 the driver
 dracut /boot/initramfs-$dir.img $dir
 fi
 done

 Can someone give me a hint on how to do what needs to be
done? I'm
 not familiar with drivers on unix systems so i'm a bit
lost, full sh
 file is attached if needed, thanks.






--
--
- Rick Stevens, Systems Engineer, AllDigital ri...@alldigital.com
 -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-   Fear is finding a ".vbs" script in your Inbox-
--
--
users mailing list
users@lists.fedoraproject.org 
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Re: Monitor / graphics card recommendation

2016-01-21 Thread Tom Horsley 
Whenever possible I try to get a motherboard that supports
native Intel graphics since there is no proprietary
driver for Intel, so you can always rely on the Intel
driver working :-). (And you don't have the hassle
of pluging in a video card that might have noisy fans).

The latest Intel chips have support for natively driving
resolutions as high as the UHD (4k) monitors.

I'm currently sitting in front of a samsung 48" TV
which I also use as my computer monitor with a little
typing table for the keyboard so I can wheel it a
comfortable distance from the TV for computer use.
(This obviously works best if you are the only one
who uses the TV).
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor / graphics card recommendation

2016-01-21 Thread thibaut noah 
I'm sitting less than 20" away from my 34" screen and this is just
priceless, for programming, music and video editing, got a 24" next to it
and there is no way i'm going back to something that small.
LG has on mac and windows the screen split feature which allow you to
divide the screen up to 4 balanced window, it's like having 4monitors in
one.
Would be a bit cumbersome to reproduce the same mechanism on linux but i'm
sure a solution can be find.
That's about the main reason to get a 21:9 screen (that and movies in
theater mode, and games off course)

2016-01-22 0:32 GMT+01:00 Doug :

>
>
> On 01/21/2016 03:02 PM, Mark wrote:
>
>> One of my new year's resolutions is to upgrade the monitor on my Fedora
>> 23 Desktop.
>>
>> I've been looking at a 34" curved 3440 x 1440 monitor. But first I want
>> to make sure it actually makes sense to get such a large monitor for
>> Linux and that there's a graphics card on the market that works well
>> with Fedora and that can drive such a large monitor. I would prefer an
>> open source driver, but I'm prepared to install a blob if I have to.
>> I'm not interested in gaming so that's not an issue, it's the real
>> estate I'm after.
>>
>> Any thoughts/recommendations?
>>
> Are you sure you really want such a large monitor? I'm sitting about 24"
> away from a 24" monitor, and I don't see how I'd want a larger one, unless
> perhaps I were doing CAD design,
> where it would be helpful to see more (or all) of whatever you're
> designing all on one page at the same time. And of course, turn your head
> to the relevant part of the screen.
>
> I would suggest you'd think hard about spending that much money on a
> monitor that you might not really want once you had it.
>
> Just a thought.
>
> --doug
>
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor / graphics card recommendation

2016-01-21 Thread DJ Delorie 

Doug  writes:
> Are you sure you really want such a large monitor?

Heh.  I have four monitors, the biggest is a 40" Seiki 4k.  Total width
is about six feet.  For my purposes, more pixels is definitely better!

(F20 with a GTX980, proprietary blob, multi-purpose)
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor / graphics card recommendation

2016-01-21 Thread Doug 



On 01/21/2016 03:02 PM, Mark wrote:

One of my new year's resolutions is to upgrade the monitor on my Fedora
23 Desktop.

I've been looking at a 34" curved 3440 x 1440 monitor. But first I want
to make sure it actually makes sense to get such a large monitor for
Linux and that there's a graphics card on the market that works well
with Fedora and that can drive such a large monitor. I would prefer an
open source driver, but I'm prepared to install a blob if I have to.
I'm not interested in gaming so that's not an issue, it's the real
estate I'm after.

Any thoughts/recommendations?

Are you sure you really want such a large monitor? I'm sitting about 24" away from a 
24" monitor, and I don't see how I'd want a larger one, unless perhaps I were doing 
CAD design,
where it would be helpful to see more (or all) of whatever you're designing all 
on one page at the same time. And of course, turn your head to the relevant 
part of the screen.

I would suggest you'd think hard about spending that much money on a monitor 
that you might not really want once you had it.

Just a thought.

--doug
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: driver install but not loaded

2016-01-21 Thread thibaut noah 
Thanks for the enlightment.
I manage to get the driver from the modules.gz archive and i made a new
initframs using dracut --add-drivers but modprobe still cannot find it,
possible that the module will indeed not work :/
The error is saying :
could not insert 'rr272x_1x' : Exec format error
Did i miss something? the driver is a .ko file

2016-01-21 18:53 GMT+01:00 Rick Stevens :

> On 01/21/2016 04:02 AM, thibaut noah wrote:
>
>> updating this, i did some testing on the sh file and i found where the
>> issue is coming from.
>> There is two for loops (at least two that concerns me) and the code
>> inside is never executed.
>> Condition is :
>> for dir in [23].*;do
>>[ -d $dir/kernel/fs ] || continue
>>
>> I'm a bit lost here, what is this 23 number? it cannot be fedora number
>> as this driver is the open source version of the fedora 17 driver.
>> Pretty sure if i modify the condition with a correct one everything
>> should work properly
>>
>
> F17? Well, that's probably the issue. What you're seeing is an attempt
> to walk down the various /lib/modules/2.* and /lib/modules/3.* trees to
> install the driver. If you're on F22 or F23, you probably don't HAVE
> 2.* or 3.* kernel trees. You have 4.x kernel trees.
>
> You could try changing that line from:
>
> for dir in [23].*; do
>
> To:
>
> for dir in [234].*; do
>
> That would include the 4.x kernel trees. I don't know if the module will
> work, though as it seems to be written for quite old kernels. YMMV
>
> 2016-01-21 12:21 GMT+01:00 thibaut noah > >:
>>
>>
>> Hello guys, got this weird error trying to install my raid driver :
>>
>> Start to install the driver rr272x_1x.ko of rr272x_1x.
>> Finish installing the kernel module rr272x_1x.ko.
>> Loading rr272x_1x driver module rr272x_1x
>> modprobe: FATAL: Module rr272x_1x not found.
>>
>> Checked with lsmod driver does not appear tough the installation is
>> finished (checked the sh file, modprobe is running at the end).
>> After a little read of the sh file i can confirm that the driver is
>> in /etc/rc.modules (it appears to be with sd_mod and that's all).
>> chmod on rc.modules in the sh file is successfull (chmod 755).
>> The failing part seems to be this :
>>
>> elif [ "${MODULE}" = "rr272x_1x" -o "${MODULE}" = "rr274x_3x" -o
>>   "${MODULE}" = "rr276x" -o "${MODULE}" = "rr278x" ] ; then
>> ( cd /lib/modules/
>> for dir in [23].*; do
>> [ -d $dir/kernel/fs ] || continue
>> if [ -f /boot/initrd-$dir.img ]; then
>> mv /boot/initrd-$dir.img /boot/initrd-$dir.img.bak
>> # do not include mvsas in initrd, as the udev and so will load the
>> driver
>> mkinitrd --builtin=mvsas /boot/initrd-$dir.img $dir
>> elif [ -f /boot/initramfs-$dir.img ]; then
>> mv /boot/initramfs-$dir.img /boot/initramfs-$dir.img.bak
>> # do not include mvsas in initramfs, as the udev and so will load
>> the driver
>> dracut /boot/initramfs-$dir.img $dir
>> fi
>> done
>>
>> Can someone give me a hint on how to do what needs to be done? I'm
>> not familiar with drivers on unix systems so i'm a bit lost, full sh
>> file is attached if needed, thanks.
>>
>>
>>
>>
>>
>
> --
> --
> - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
> - AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
> --
> -   Fear is finding a ".vbs" script in your Inbox-
> --
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: NFS URLs in Nautilus on Fedora 22 stopped working

2016-01-21 Thread Rick Stevens 

On 01/21/2016 02:30 PM, Ranbir wrote:

On Wed, 2016-01-20 at 14:58 -0500, Ranbir wrote:

I don't know or how, but I can no longer browse nfs shares from
Nautilus. If I type in a NFS URLs, Nautilus immediatly says it's not
recognized. All of my NFS bookmarks stopped working, too.

My NFS server is running just fine. This seems to be a "problem" on
the
Fedora end.


Is there no love for this thread? :( I still don't know why Nautilus
has all of a sudden stopped working with nfs URLs.


Is your NFS server doing NFSV3 or NFSV4? "showmount -e" doesn't work if
the server is NFSV4 and I suspect that's what Nautilus is doing (or
something like it).

If you have access to the NFS server, try altering the options to the
nfsd daemon to not offer V4/V4.1. This can be done by passing it the
"-V 3" or "-N 4" options (or you can edit the "RPCNFSDARGS" variable
in /etc/sysconfig/nfs, put the option in there and "systemctl restart 
nfs-config") and try browsing it again.


This is a shot in the dark here. It's bitten some of our people here.
They could mount the exports, but not browse them.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
- If at first you don't succeed, quit. No sense being a damned fool! -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor / graphics card recommendation

2016-01-21 Thread thibaut noah 
I possess a lg 34" (the curved one), you can run it just fine with intel
integrated graphics (my processor is a i7 4790k) if you don't use display
heavy applications (like games).
You can also play very well with a dedicated graphic card and a gaming
virtual machine (using vga passthrough and something like a gtx 980ti to
run games well), in case you change your mind about gaming someday.
Biggest downside i found was that it was impossible for me to see my bios
menu with this screen, i have no idea if this is grub related since i
purchased the screen for my gaming vm, easily fix with a second screen
which i use only for my fedora host.
Anyway, since you won't play, if you can find the reason of the issue i got
and fix it you won't have any problem at all. You won't even need to
install a specific driver.

2016-01-21 21:45 GMT+01:00 Wolfgang S. Rupprecht <
wolfgang.ruppre...@gmail.com>:

>
> Mark  writes:
> > One of my new year's resolutions is to upgrade the monitor on my Fedora
> > 23 Desktop.
> >
> > I've been looking at a 34" curved 3440 x 1440 monitor. But first I want
> > to make sure it actually makes sense to get such a large monitor for
> > Linux and that there's a graphics card on the market that works well
> > with Fedora and that can drive such a large monitor. I would prefer an
> > open source driver, but I'm prepared to install a blob if I have to.
> > I'm not interested in gaming so that's not an issue, it's the real
> > estate I'm after.
>
> Have a look at the ASUS R7360-OC-2GD5 or the same ATI/Radeon R7-360 card
> by any of a half dozen companies.  I have one attached to a cheap 4k
> Seiki HDMI monitor (8M pixels) which is 3M pixels more than you need to
> shift
> (5M pixels).  Xorg works with it out of the box.  No mystery binaries
> needed.
>
> The downside is this card has a fan, but it runs very slowly under Xorg
> and normal use.  Modern framebuffers just don't come fanless any more.
> The GPU's at idle all seem to use just a touch too much power.
>
> -wolfgang
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: NFS URLs in Nautilus on Fedora 22 stopped working

2016-01-21 Thread Ranbir 
On Wed, 2016-01-20 at 14:58 -0500, Ranbir wrote:
> I don't know or how, but I can no longer browse nfs shares from
> Nautilus. If I type in a NFS URLs, Nautilus immediatly says it's not
> recognized. All of my NFS bookmarks stopped working, too.
> 
> My NFS server is running just fine. This seems to be a "problem" on
> the
> Fedora end.

Is there no love for this thread? :( I still don't know why Nautilus
has all of a sudden stopped working with nfs URLs.


-- 
Ranbir


signature.asc
Description: This is a digitally signed message part
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor / graphics card recommendation

2016-01-21 Thread Wolfgang S. Rupprecht 

Mark  writes:
> One of my new year's resolutions is to upgrade the monitor on my Fedora
> 23 Desktop.
>
> I've been looking at a 34" curved 3440 x 1440 monitor. But first I want
> to make sure it actually makes sense to get such a large monitor for
> Linux and that there's a graphics card on the market that works well
> with Fedora and that can drive such a large monitor. I would prefer an
> open source driver, but I'm prepared to install a blob if I have to.
> I'm not interested in gaming so that's not an issue, it's the real
> estate I'm after. 

Have a look at the ASUS R7360-OC-2GD5 or the same ATI/Radeon R7-360 card
by any of a half dozen companies.  I have one attached to a cheap 4k
Seiki HDMI monitor (8M pixels) which is 3M pixels more than you need to shift
(5M pixels).  Xorg works with it out of the box.  No mystery binaries
needed.

The downside is this card has a fan, but it runs very slowly under Xorg
and normal use.  Modern framebuffers just don't come fanless any more.
The GPU's at idle all seem to use just a touch too much power.

-wolfgang
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor / graphics card recommendation

2016-01-21 Thread Mark 
On Thu, 2016-01-21 at 18:21 -0200, Bernardo Sulzbach wrote:
> To be the guy that answers a question with a question, have you
> considered multiple smaller monitors?

Yes, I have, but would prefer one large one, if it works with Linux.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Monitor / graphics card recommendation

2016-01-21 Thread Bernardo Sulzbach 
On Thu, Jan 21, 2016 at 6:02 PM, Mark  wrote:
> One of my new year's resolutions is to upgrade the monitor on my Fedora
> 23 Desktop.
>
> I've been looking at a 34" curved 3440 x 1440 monitor. But first I want
> to make sure it actually makes sense to get such a large monitor for
> Linux and that there's a graphics card on the market that works well
> with Fedora and that can drive such a large monitor. I would prefer an
> open source driver, but I'm prepared to install a blob if I have to.
> I'm not interested in gaming so that's not an issue, it's the real
> estate I'm after.
>

To be the guy that answers a question with a question, have you
considered multiple smaller monitors?

-- 
Bernardo Sulzbach
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Monitor / graphics card recommendation

2016-01-21 Thread Mark 
One of my new year's resolutions is to upgrade the monitor on my Fedora
23 Desktop.

I've been looking at a 34" curved 3440 x 1440 monitor. But first I want
to make sure it actually makes sense to get such a large monitor for
Linux and that there's a graphics card on the market that works well
with Fedora and that can drive such a large monitor. I would prefer an
open source driver, but I'm prepared to install a blob if I have to.
I'm not interested in gaming so that's not an issue, it's the real
estate I'm after. 

Any thoughts/recommendations?
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: WARNING regarding 4.3.x kernel

2016-01-21 Thread Patrick O'Callaghan 
On Thu, 2016-01-21 at 12:22 -0700, Chris Murphy wrote:
> Weird. I've been using virt-manager with kernel 4.3.3 and 4.4.0 on
> Fedora 23 for some time without problems. Maybe check AVC messages?
> 
> ausearch -m AVC
> 
> Maybe it's worth relabeling:
> 
> restorecon -rv /
> 
> I don't know why but even after a clean install and no updates,
> restorecon fixes labels. It's like they aren't set correctly to start
> with for some reason. And then after any update I run it and it fixes
> more things each time. Kinda annoying really. I don't feel like I
> ought to need to relabel manually after every update. Maybe more than
> one label is valid, just that one is more valid than another and
> that's why the install label is sometimes different from post-install
> label.

How is this related to the topic of this thread?

poc
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: WARNING regarding 4.3.x kernel

2016-01-21 Thread Chris Murphy 
Weird. I've been using virt-manager with kernel 4.3.3 and 4.4.0 on
Fedora 23 for some time without problems. Maybe check AVC messages?

ausearch -m AVC

Maybe it's worth relabeling:

restorecon -rv /

I don't know why but even after a clean install and no updates,
restorecon fixes labels. It's like they aren't set correctly to start
with for some reason. And then after any update I run it and it fixes
more things each time. Kinda annoying really. I don't feel like I
ought to need to relabel manually after every update. Maybe more than
one label is valid, just that one is more valid than another and
that's why the install label is sometimes different from post-install
label.

Chris Murphy
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

4.3.3-300 DMAR: DMAR:[DMA Write] Request device [8a:06.1] fault addr fc26e000

2016-01-21 Thread Nate Pearlstein 
Seeing errors after upgrading from 4.2.8-300 to 4.3.3-300, I also see the same 
errors on newer kernels for f23 from koji and 
4.5.0-0.rc0.git6.1.vanilla.knurd.1


dmesg | egrep -i ‘mlx|dmar'

[   17.816756] mlx4_core :82:00.0: Mapped 1 chunks/256 KB at 12004 for 
ICM
[   17.825330] mlx4_core :8a:00.0: SRIOV, disabling HA mode for intf proto 0
[   17.825541]  mlx4_ib_add: counter index 0 for port 1 allocated 0
[   17.833869]  mlx4_ib_add: counter index 1 for port 2 allocated 0
[   17.906397] mlx4_core :8a:00.0: Mapped 1 chunks/256 KB at 12004 for 
ICM
[   17.911403] mlx4_core :8a:00.0: mlx4_ib: multi-function enabled
[   17.925065] mlx4_core :8a:00.0: mlx4_ib: initializing demux service for 
128 qp1 clients
[   17.937459] mlx4_core :8a:00.0: Mapped 1 chunks/256 KB at 12804 for 
ICM
[   17.938766] mlx4_core :8a:00.0: Mapped 1 chunks/256 KB at 1200c for 
ICM
[   29.527780] mlx4_core :8a:00.0: Mapped 1 chunks/256 KB at 12808 for 
ICM
[   29.529083] mlx4_core :8a:00.0: Mapped 1 chunks/256 KB at 12014 for 
ICM
[   31.330799] DMAR: DRHD: handling fault status reg 2
[   31.330803] DMAR: DMAR:[DMA Write] Request device [8a:06.1] fault addr 
fc26e000
  DMAR:[fault reason 02] Present bit in context entry is clear
[   31.330865] DMAR: DRHD: handling fault status reg 102
[   31.330868] DMAR: DMAR:[DMA Read] Request device [8a:06.1] fault addr 
fc632000
  DMAR:[fault reason 02] Present bit in context entry is clear
[   31.530006] DMAR: DRHD: handling fault status reg 202
.
.
.

All previous f22 and f23 releases I’ve used were fine.

I have two IB cards: all Firmware version: 2.9.1000

82:00.0 InfiniBand: Mellanox Technologies MT26428 [ConnectX VPI PCIe 2.0 5GT/s 
- IB QDR / 10GigE] (rev b0)
8a:00.0 InfiniBand: Mellanox Technologies MT26428 [ConnectX VPI PCIe 2.0 5GT/s 
- IB QDR / 10GigE] (rev b0)

The first one has sriov off the second has sriov on.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: driver install but not loaded

2016-01-21 Thread Rick Stevens 

On 01/21/2016 04:02 AM, thibaut noah wrote:

updating this, i did some testing on the sh file and i found where the
issue is coming from.
There is two for loops (at least two that concerns me) and the code
inside is never executed.
Condition is :
for dir in [23].*;do
   [ -d $dir/kernel/fs ] || continue

I'm a bit lost here, what is this 23 number? it cannot be fedora number
as this driver is the open source version of the fedora 17 driver.
Pretty sure if i modify the condition with a correct one everything
should work properly


F17? Well, that's probably the issue. What you're seeing is an attempt
to walk down the various /lib/modules/2.* and /lib/modules/3.* trees to 
install the driver. If you're on F22 or F23, you probably don't HAVE

2.* or 3.* kernel trees. You have 4.x kernel trees.

You could try changing that line from:

for dir in [23].*; do

To:

for dir in [234].*; do

That would include the 4.x kernel trees. I don't know if the module will
work, though as it seems to be written for quite old kernels. YMMV


2016-01-21 12:21 GMT+01:00 thibaut noah mailto:thibaut.n...@gmail.com>>:

Hello guys, got this weird error trying to install my raid driver :

Start to install the driver rr272x_1x.ko of rr272x_1x.
Finish installing the kernel module rr272x_1x.ko.
Loading rr272x_1x driver module rr272x_1x
modprobe: FATAL: Module rr272x_1x not found.

Checked with lsmod driver does not appear tough the installation is
finished (checked the sh file, modprobe is running at the end).
After a little read of the sh file i can confirm that the driver is
in /etc/rc.modules (it appears to be with sd_mod and that's all).
chmod on rc.modules in the sh file is successfull (chmod 755).
The failing part seems to be this :

elif [ "${MODULE}" = "rr272x_1x" -o "${MODULE}" = "rr274x_3x" -o
  "${MODULE}" = "rr276x" -o "${MODULE}" = "rr278x" ] ; then
( cd /lib/modules/
for dir in [23].*; do
[ -d $dir/kernel/fs ] || continue
if [ -f /boot/initrd-$dir.img ]; then
mv /boot/initrd-$dir.img /boot/initrd-$dir.img.bak
# do not include mvsas in initrd, as the udev and so will load the
driver
mkinitrd --builtin=mvsas /boot/initrd-$dir.img $dir
elif [ -f /boot/initramfs-$dir.img ]; then
mv /boot/initramfs-$dir.img /boot/initramfs-$dir.img.bak
# do not include mvsas in initramfs, as the udev and so will load
the driver
dracut /boot/initramfs-$dir.img $dir
fi
done

Can someone give me a hint on how to do what needs to be done? I'm
not familiar with drivers on unix systems so i'm a bit lost, full sh
file is attached if needed, thanks.







--
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-   Fear is finding a ".vbs" script in your Inbox-
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: WARNING regarding 4.3.x kernel

2016-01-21 Thread Cristian Sava 
On Thu, 2016-01-21 at 11:55 +0100, thibaut noah wrote:
> Did you report it? seems like someone forgot to check the pointer
> before accessing it.
Not yet. Further investigation is needed.
What I've done now in virtual environment:
1-Install F23 server, default, no options.
2-Update, reboot
3-Install minimal X:
  dnf groupinstall base-x
  dnf install xterm xorg-x11-xbitmaps xorg-x11-fonts-ISO8859-15-75dpi
xorg-x11-fonts-ISO8859-15-100dpi xorg-x11-fonts-misc
  dnf install xorg-x11-xdm xorg-x11-xsm xorg-x11-xkb-extras xorg-x11-
xfs xorg-x11-xfs-utils xorg-x11-twm
4-Install VM environment:
  dnf install qemu qemu-common qemu-guest-agent qemu-img qemu-kvm qemu-
kvm-tools qemu-user qemu-system-x86
  dnf install libvirt virt-manager virt-install
5-Switch to graphical and the error is there:
  su -c virt-manager
6-Reboot and add very basic gnome:
  dnf install gnome-desktop3 gnome-commander gnome-abrt gnome-disk-
utility gnome-menus gnome-shell gnome-shell-extension-common gnome-
terminal gnome-themes-standard gnome-tweak-tool
7-reboot, switch to graphical:
 a) Still error in xterm: su -c virt-manager
 b) Surprise: the VM icon works as expected!
Same result on a phisical machine with the difference that trying to
switch back to multi-user freezes the box.
Anyone else want to test it?

> 2016-01-21 9:12 GMT+01:00 Cristian Sava :
> > I have a F23 server with minimal working X (no desktop).
> > All was working well with kernel-4.2.x
> > With kernel-4.3.x I get (in xterm):
> > 
> > [a53@s ~]$ su -c virt-manager
> > Password: 
> > [a53@s ~]$ No protocol specified
> > Unable to init server: Could not connect: Connection refused
> > (virt-manager:54862): Gtk-CRITICAL **: gtk_settings_get_for_screen:
> > assertion 'GDK_IS_SCREEN (screen)' failed
> > [a53@s ~]$ 
> > 
> > journalctl gives:
> > 
> > kernel: virt-manager[8896]: segfault at 0 ip 7f612fce78a9 sp
> > 7ffe5a45e580 error 4 in libgtk-
> > 3.so.0.1800.6[7f612fa2d000+71]
> > kernel: BUG: unable to handle kernel NULL pointer dereference at
> > 0060
> > 
> > Searching the web I discovered that during years this error shows
> > up
> > from time to time across different distributions (including
> > Fedora).
> > This time it seems to be kernel related and does not show up with
> > Gnome.
> > 
> > C.S
> > 

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: driver install but not loaded

2016-01-21 Thread thibaut noah 
updating this, i did some testing on the sh file and i found where the
issue is coming from.
There is two for loops (at least two that concerns me) and the code inside
is never executed.
Condition is :
for dir in [23].*;do
  [ -d $dir/kernel/fs ] || continue

I'm a bit lost here, what is this 23 number? it cannot be fedora number as
this driver is the open source version of the fedora 17 driver.
Pretty sure if i modify the condition with a correct one everything should
work properly

2016-01-21 12:21 GMT+01:00 thibaut noah :

> Hello guys, got this weird error trying to install my raid driver :
>
> Start to install the driver rr272x_1x.ko of rr272x_1x.
> Finish installing the kernel module rr272x_1x.ko.
> Loading rr272x_1x driver module rr272x_1x
> modprobe: FATAL: Module rr272x_1x not found.
>
> Checked with lsmod driver does not appear tough the installation is
> finished (checked the sh file, modprobe is running at the end).
> After a little read of the sh file i can confirm that the driver is in
> /etc/rc.modules (it appears to be with sd_mod and that's all).
> chmod on rc.modules in the sh file is successfull (chmod 755).
> The failing part seems to be this :
>
> elif [ "${MODULE}" = "rr272x_1x" -o "${MODULE}" = "rr274x_3x" -o
>  "${MODULE}" = "rr276x" -o "${MODULE}" = "rr278x" ] ; then
> ( cd /lib/modules/
> for dir in [23].*; do
> [ -d $dir/kernel/fs ] || continue
> if [ -f /boot/initrd-$dir.img ]; then
> mv /boot/initrd-$dir.img /boot/initrd-$dir.img.bak
> # do not include mvsas in initrd, as the udev and so will load the driver
> mkinitrd --builtin=mvsas /boot/initrd-$dir.img $dir
> elif [ -f /boot/initramfs-$dir.img ]; then
> mv /boot/initramfs-$dir.img /boot/initramfs-$dir.img.bak
> # do not include mvsas in initramfs, as the udev and so will load the
> driver
> dracut /boot/initramfs-$dir.img $dir
> fi
> done
>
> Can someone give me a hint on how to do what needs to be done? I'm not
> familiar with drivers on unix systems so i'm a bit lost, full sh file is
> attached if needed, thanks.
>
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

driver install but not loaded

2016-01-21 Thread thibaut noah 
Hello guys, got this weird error trying to install my raid driver :

Start to install the driver rr272x_1x.ko of rr272x_1x.
Finish installing the kernel module rr272x_1x.ko.
Loading rr272x_1x driver module rr272x_1x
modprobe: FATAL: Module rr272x_1x not found.

Checked with lsmod driver does not appear tough the installation is
finished (checked the sh file, modprobe is running at the end).
After a little read of the sh file i can confirm that the driver is in
/etc/rc.modules (it appears to be with sd_mod and that's all).
chmod on rc.modules in the sh file is successfull (chmod 755).
The failing part seems to be this :

elif [ "${MODULE}" = "rr272x_1x" -o "${MODULE}" = "rr274x_3x" -o
 "${MODULE}" = "rr276x" -o "${MODULE}" = "rr278x" ] ; then
( cd /lib/modules/
for dir in [23].*; do
[ -d $dir/kernel/fs ] || continue
if [ -f /boot/initrd-$dir.img ]; then
mv /boot/initrd-$dir.img /boot/initrd-$dir.img.bak
# do not include mvsas in initrd, as the udev and so will load the driver
mkinitrd --builtin=mvsas /boot/initrd-$dir.img $dir
elif [ -f /boot/initramfs-$dir.img ]; then
mv /boot/initramfs-$dir.img /boot/initramfs-$dir.img.bak
# do not include mvsas in initramfs, as the udev and so will load the driver
dracut /boot/initramfs-$dir.img $dir
fi
done

Can someone give me a hint on how to do what needs to be done? I'm not
familiar with drivers on unix systems so i'm a bit lost, full sh file is
attached if needed, thanks.


install.sh
Description: Bourne shell script
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: WARNING regarding 4.3.x kernel

2016-01-21 Thread thibaut noah 
Did you report it? seems like someone forgot to check the pointer before
accessing it.

2016-01-21 9:12 GMT+01:00 Cristian Sava :

> I have a F23 server with minimal working X (no desktop).
> All was working well with kernel-4.2.x
> With kernel-4.3.x I get (in xterm):
>
> [a53@s ~]$ su -c virt-manager
> Password:
> [a53@s ~]$ No protocol specified
> Unable to init server: Could not connect: Connection refused
> (virt-manager:54862): Gtk-CRITICAL **: gtk_settings_get_for_screen:
> assertion 'GDK_IS_SCREEN (screen)' failed
> [a53@s ~]$
>
> journalctl gives:
>
> kernel: virt-manager[8896]: segfault at 0 ip 7f612fce78a9 sp
> 7ffe5a45e580 error 4 in libgtk-3.so.0.1800.6[7f612fa2d000+71]
> kernel: BUG: unable to handle kernel NULL pointer dereference at
> 0060
>
> Searching the web I discovered that during years this error shows up
> from time to time across different distributions (including Fedora).
> This time it seems to be kernel related and does not show up with
> Gnome.
>
> C.S
>
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

WARNING regarding 4.3.x kernel

2016-01-21 Thread Cristian Sava 
I have a F23 server with minimal working X (no desktop).
All was working well with kernel-4.2.x
With kernel-4.3.x I get (in xterm):

[a53@s ~]$ su -c virt-manager
Password: 
[a53@s ~]$ No protocol specified
Unable to init server: Could not connect: Connection refused
(virt-manager:54862): Gtk-CRITICAL **: gtk_settings_get_for_screen:
assertion 'GDK_IS_SCREEN (screen)' failed
[a53@s ~]$ 

journalctl gives:

kernel: virt-manager[8896]: segfault at 0 ip 7f612fce78a9 sp
7ffe5a45e580 error 4 in libgtk-3.so.0.1800.6[7f612fa2d000+71]
kernel: BUG: unable to handle kernel NULL pointer dereference at
0060

Searching the web I discovered that during years this error shows up
from time to time across different distributions (including Fedora).
This time it seems to be kernel related and does not show up with
Gnome.

C.S

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org