search for: fb1

Dear All, I am analysing some data for a colleague (not my data, gotta be published so I cannot divulge). My response variable is the number of matings observed per day for some fruitlies. My factors are: Day: the observations were taken on 9 days Regime: 3 selection regimes Line: 3 replicates per selection regime. I have 81 observations in total The lines are coded A to I, so I do not need

Een ingesloten tekst met niet-gespecificeerde tekenset is van het bericht gescrubt ... Naam: niet beschikbaar Url: https://stat.ethz.ch/pipermail/r-help/attachments/20071029/b29e9bd5/attachment.pl

...r in integrate(int2, lower = 0, upper = t) : the integral is probably divergent. I could not found any theoretical interpretation of it. I'm sending the code : ######################################################################################### f3<-function(t,r){ #calculation for t1 fb1<-function(t,r){ v1<-numeric(0) for(j in 1:r){ int1<-function(x1){ int_1<- (1/p+log(x1/lamda))^2 * j * choose(n,j) * (pweibull(x1,shape=p,scale=lamda))^(j-1) * (1 - pweibull(x1,shape=p,scale=lamda))^(n-j) * dweibull(x1,shape=p,scale=lamda) int_1 } v1[j]<-integrate(int1,lower=0,upper=...

I have only verified the fix on Debian 7. The Debian 6 guest doesn't appear to boot, I'm not sure why. The second patch contains a test suite. Rich.

In thinking about this we could use a Mutex::tryacquire(...) (non-recursive), around JIT::runJITOnFunctionUnlocked(...)'s while loop, and use your JITEmitter:: getLazyFunctionStub(...) suggestion in place of forceEmitFunctionStub(...). Is the lock attempt too heavy, even if it is implemented with atomics? I'll implement this when I have time. Garrison On Feb 17, 2010, at 15:42, Garrison

...where the GeForce 8600 GTS is a secondary GPU and not initialized by VBIOS? If I'm booting on GF as primary GPU nouveau gets along with it. It's in the case I'm booting on the radeon (and GF is thus left alone by BIOS) that things are broken. Modprobe nouveau works, writing to its /dev/fb1 seems to work as well (though monitor connected to GF via VGA cable sees no signal). Launching kmscon freezes the whole system: kmscon --drm --gpus=all -v --debug [0000.000000] NOTICE: kmscon Revision kmscon-8 Oct 26 2014 19:43:16 [0000.000101] INFO: conf: reading config file /etc/kmscon/kmscon.co...

...light interface available, not registering our own [ 3.327452] [drm] nouveau 0000:01:00.0: allocated 1024x768 fb: 0xe0000, bo ffff880243525400 [ 3.327455] checking generic (b0000000 410000) vs hw (c0000000 10000000) [ 3.327456] checking generic (b0000000 410000) vs hw (d0000000 2000000) [ 3.327702] fb1: nouveaufb frame buffer device [ 3.327704] drm: registered panic notifier [ 3.327708] [drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0 Instead in 3.4.3: [ 2.643224] [drm] Initialized drm 1.1.0 20060810 [ 2.644723] wmi: Mapper loaded [ 2.647064] MXM: GUID detected in BIOS [ 2.6...

.../ctxgf100.c:1365/gf100_grctx_generate()! [ 306.473775] nouveau 0000:01:00.0: gr: failed to construct context [ 306.473778] nouveau 0000:01:00.0: gr: init failed, -16 [ 306.476140] nouveau 0000:01:00.0: DRM: allocated 1680x1050 fb: 0x60000, bo ffff88068c051400 [ 306.476221] nouveau 0000:01:00.0: fb1: nouveaufb frame buffer device [ 306.476226] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1 -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop...

...install the OS with the live cd (like you can with Ubuntu). I don't have easy access to Linux or spare computers, so I used my Windows laptop to dd to the USB. ********************************************** C:\installs\dd>dd if=c:\installs\CentOS-5.3-i386-bin-dvd.iso of=\\.\Volume{5a5e4 fb1-b53a-11dd-b7f4-001492190322} --size --progress bs=1M rawwrite dd for windows version 0.5. Written by John Newbigin <jn at it.swin.edu.au> This program is covered by the GPL. See copying.txt for details 3,971,014,656 3787+1 records in 3787+1 records out ***************************************...

...2 (21.10.2013). [drm] Driver supports precise vblank timestamp query. memmap_init_zone_device initialised 2097152 pages in 16ms nouveau 0000:01:00.0: DRM: DMEM: registered 8192MB of device memory nouveau 0000:01:00.0: DRM: allocated 2560x1600 fb: 0x200000, bo 0000000018f13ee1 nouveau 0000:01:00.0: fb1: nouveaudrmfb frame buffer device sauron:~$ xrandr --setprovideroutputsource 1 0 sauron:~$ xrandr --listactivemonitors Monitors: 1 0: +*eDP-1 3840/382x2160/214+0+0 eDP-1 sauron:~$ xrandr --auto sauron:~$ xrandr --listactivemonitors Monitors: 2 0: +*eDP-1 3840/382x2160/214+0+0 eDP-1 1: +HDM...

...rm] Cannot find any crtc or sizes - going 1024x768 [ 174.619661] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000401 FAULT at 0x002010 [ IBUS TIMEOUT ] [ 174.711581] nouveau [ DRM] allocated 1024x768 fb: 0x60000, bo f653bc00 [ 174.711815] nouveau 0000:01:00.0: fb1: nouveaufb frame buffer device [ 174.711824] [drm] Initialized nouveau 1.1.1 20120801 for 0000:01:00.0 on minor 1 [ 174.714771] After "modprobe nouveau" 3) Can't switch to dedicated graphics card 3.1) Switch to Nvidia card Result: Screen turns off (inc...

...oltage 610mV [drm] nouveau 0000:01:00.0: 3: core 1000MHz shader 2000MHz memory 1080MHz voltage 630mV [drm] nouveau 0000:01:00.0: 4: core 1254MHz shader 2508MHz memory 1080MHz voltage 630mV [drm] nouveau 0000:01:00.0: c: [drm] nouveau 0000:01:00.0: allocated 1024x768 fb: 0xe0000, bo ffff88026308c000 fb1: nouveaufb frame buffer device [drm] Initialized nouveau 1.0.0 20120316 for 0000:01:00.0 on minor 1 -- Daniel J Blueman

...[ 2.050859] [drm] nouveau 0000:02:00.0: 0 available performance level(s) [ 2.050861] [drm] nouveau 0000:02:00.0: c: core 50MHz shader 101MHz memory 135MHz voltage 963mV fanspeed 40% [ 2.334686] [drm] nouveau 0000:02:00.0: allocated 1024x768 fb: 0x1e0000, bo ffff88031b80a800 [ 2.334862] fb1: nouveaufb frame buffer device [ 2.334865] [drm] Initialized nouveau 1.0.0 20120316 for 0000:02:00.0 on minor 1 [ 1642.831909] [drm] nouveau 0000:01:00.0: illegal object class: 0x906e [ 1642.831911] [drm] nouveau 0000:01:00.0: Error creating object: -22 (1/0x001f906e) [ 4730.269562] [drm] nouvea...

On 2018-02-14 — 09:36, Ilia Mirkin wrote: > On Wed, Feb 14, 2018 at 9:35 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos <mroos at linux.ee> wrote: > >>> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: > >> > >> NV5 in another PC (secondary card in x86-64) made the systrem

On Fri, May 29, 2020 at 02:53:51PM -0400, Ilia Mirkin wrote: > > moving to new window moves the mouse, but not windows get displayed. > > Do you see anything in dmesg after this is set up? I'd expect some > errors about timeouts or something else. Nothing other than what I pasted. > Which kernel are you using? There have been some turing-specific fixes recently. 5.5.11.

...=(1973.01, 2000.12) # period=12 # file="blp.dat" # format="datevalue" # } # x11{ # mode=mult # sigmalim=(1.8 2.8) # seasonalma=x11default # trendma=13 # appendfcst=no # save=(b1 c17 d10 d11 d12 d13) # savelog=(m1 m2 m3 m4 m5 m6 m7 m8 m9 m10 m11 q q2 msr icr fb1 fd8 msf ids) # } # execute the x12 fortran pgm. executable x12a stored in /home/fred/x12a system("/home/fred/x12a/x12a blp") # read x12 fortran pgm output tables back into R blp.x12 <- readx12out("blp", adtype="M", calendar=F, tblnames=NULL) # basic versio...

Hi Olivier, Thanks for responding! I get to learn this way. On Feb 17, 2010, at 12:50, Olivier Meurant wrote: > Hi Garrison, > > I am not a specialist of the code but here is my 2 cents: > > - I like the idea that in lazy-mode the call (in module or not) is treated by a stub (like every calls). If we go further with this, I'll have to add test cases for lazy mode. I kind

...m] Driver supports precise vblank timestamp query. > memmap_init_zone_device initialised 2097152 pages in 16ms > nouveau 0000:01:00.0: DRM: DMEM: registered 8192MB of device memory > nouveau 0000:01:00.0: DRM: allocated 2560x1600 fb: 0x200000, bo 0000000018f13ee1 > nouveau 0000:01:00.0: fb1: nouveaudrmfb frame buffer device > > sauron:~$ xrandr --setprovideroutputsource 1 0 > sauron:~$ xrandr --listactivemonitors > Monitors: 1 > 0: +*eDP-1 3840/382x2160/214+0+0 eDP-1 > > sauron:~$ xrandr --auto > sauron:~$ xrandr --listactivemonitors > Monitors: 2 > 0:...

...01:00.0: DRM: allocated 1024x768 fb: 0x60000, bo ffff88046c748000 [ 1.668461] clocksource: Switched to clocksource tsc [ 2.406679] Console: switching to colour frame buffer device 240x67 [ 2.423231] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 2.423357] nouveau 0000:01:00.0: fb1: nouveaufb frame buffer device [ 2.423364] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1 I am running kernel-4.11.2 and xorg-server-1.19.3. I attach the full dmesg output and config file Thanks a lot for your help -- You are receiving this mail because: You are the QA...

Hey all, I've just pushed out the initial Nouveau support for $subject \o/ As the atomic modesetting transition is basically a rewrite of the KMS portion of the driver, I would be very grateful for any additional testing that people could provide (even as simple as just booting and making sure you get a display is valuable). There's a Linux tree at