Displaying 20 results from an estimated 185 matches for "boot0".
Did you mean:
boot
2004 Dec 07
1
Unprivileged user can write to mbr
...nly access to /dev/ar0:
%id
uid=1004(bztest) gid=1004(test) groups=1004(test), 5(operator)
%ls -l /dev/ar0
crw-r----- 1 root operator 4, 21 Nov 23 17:34 /dev/ar0
- Now, the device ar0 has the standard mbr installed:
%cmp /dev/ar0 /boot/mbr
/dev/ar0 /boot/mbr differ: char 447, line 1
- The boot0cfg program does not have any setuid bits:
%ls -l /usr/sbin/boot0cfg
-r-xr-xr-x 1 root wheel 7940 Oct 26 22:47 /usr/sbin/boot0cfg
- The test user now uses boot0cfg to install the boot0 bootblock:
%boot0cfg -B -b /boot/boot0 /dev/ar0
%cmp /dev/ar0 /boot/mbr
/dev/ar0 /boot/mbr differ: char 13, l...
2020 Apr 28
3
[PATCH v3 1/3] device: rework mmio mapping code to get rid of second map
...drm/nouveau/nvkm/engine/device/base.c
index 8ebbe1656..37589f365 100644
--- a/drm/nouveau/nvkm/engine/device/base.c
+++ b/drm/nouveau/nvkm/engine/device/base.c
@@ -2935,7 +2935,7 @@ nvkm_device_ctor(const struct nvkm_device_func *func,
struct nvkm_subdev *subdev;
u64 mmio_base, mmio_size;
u32 boot0, strap;
- void __iomem *map;
+ void __iomem *map = NULL;
int ret = -EEXIST, i;
unsigned chipset;
@@ -2961,12 +2961,17 @@ nvkm_device_ctor(const struct nvkm_device_func *func,
mmio_base = device->func->resource_addr(device, 0);
mmio_size = device->func->resource_size(device, 0)...
2015 Oct 06
2
Chipset & Family
4.1.8-200.fc22.x86_64 dmesg:
[ 11.809467] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x098200a2
[ 11.809493] nouveau [ DEVICE][0000:02:00.0] Chipset: G98 (NV98)
[ 11.809508] nouveau [ DEVICE][0000:02:00.0] Family : NV50
4.3.0-0.rc4.git0.1.fc24.x86_64 dmesg:
[ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2)
Where vanished these Chipset & Family super cool...
2020 Apr 17
2
[PATCH 1/3] device: use the correct mmio size when mapping
Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs.
Signed-off-by: Karol Herbst <kherbst at redhat.com>
---
drm/nouveau/nvkm/engine/device/base.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c
index 8ebbe1656..17676c75a 100644
--- a/drm/nouveau/nvkm/engine/device/base.c
+++
2020 Apr 17
2
[PATCH v2 1/3] device: use the correct mmio size when mapping
Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs.
Signed-off-by: Karol Herbst <kherbst at redhat.com>
---
drm/nouveau/nvkm/engine/device/base.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c
index 8ebbe1656..17676c75a 100644
--- a/drm/nouveau/nvkm/engine/device/base.c
+++
2015 Jan 29
28
[Bug 88868] New: PowerPC e5500, kernel crash, GT520, GT610
...er we get kernel crash.
We used several kernels ver. 3.x but on all kernels we have same error. And try
to test several nvidia card GT520, GT610 and other.
I tryed to solve the problem by myself and added some debug codes:
1. I added the following debug codes into the file base.c
/* read boot0 and strapping information */
boot0 = ioread32_native(map + 0x000000);
strap = ioread32_native(map + 0x101000);
iounmap(map);
printk ("##boot0=%x\n",boot0);
printk ("##strap=%x\n",strap);
The result you can see in the log_gt610 attachmen...
2015 Oct 06
2
Chipset & Family
...ir family. But there is the wiki page to help for that.
Regards,
Pierre
> On 06 Oct 2015, at 15:01, poma <pomidorabelisima at gmail.com> wrote:
>
>> On 06.10.2015 02:21, poma wrote:
>> 4.1.8-200.fc22.x86_64 dmesg:
>> [ 11.809467] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x098200a2
>> [ 11.809493] nouveau [ DEVICE][0000:02:00.0] Chipset: G98 (NV98)
>> [ 11.809508] nouveau [ DEVICE][0000:02:00.0] Family : NV50
>>
>>
>> 4.3.0-0.rc4.git0.1.fc24.x86_64 dmesg:
>> [ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2)...
2019 Apr 03
2
Kickstart putting /boot on sda2 (anaconda partition enumeration)?
...up with my swap partition on sda1, /boot on sda2, and
root on sda3. for $REASONS I want /boot to be the partition #1 (sda1)
My kickstart storage config looks like this:
bootloader --location=mbr --driveorder=sda,sdb
zerombr
ignoredisk --only-use=sda,sdb
clearpart --all --drives=sda,sdb
part raid.boot0 --size 1000 --ondrive=sda
part raid.swap0 --size 8192 --ondrive=sda
part raid.root0 --size 8000 --grow --ondrive=sda
part raid.boot1 --size 1000 --ondrive=sdb
part raid.swap1 --size 8192 --ondrive=sdb
part raid.root1 --size 8000 --grow --ondrive=sdb
raid /boot --fstype ext4 --device md0 --level=RAI...
2020 Oct 05
2
[PATCH] device: return error for unknown chipsets
...4
--- a/drm/nouveau/nvkm/engine/device/base.c
+++ b/drm/nouveau/nvkm/engine/device/base.c
@@ -3149,6 +3149,7 @@ nvkm_device_ctor(const struct nvkm_device_func *func,
case 0x168: device->chip = &nv168_chipset; break;
default:
nvdev_error(device, "unknown chipset (%08x)\n", boot0);
+ ret = -ENOSYS;
goto done;
}
--
2.26.2
2003 Apr 06
3
Weird boot loader
...> waits on somebody to push F1 . . . .
"Brad" replied:
> It should automatically boot the last partition you
> selected to boot (after a few seconds).
Specifically, it will boot on its own after 10 seconds (unless you
changed the "ticks" setting via the "boot0cfg" command). See "man
boot0cfg" for more details.
> You have to have a bootloader to take the next step
> in starting your computer (loading the OS).
True, but if a system will only be running FreeBSD (and only from
a single partition), there are a few ways to reduc...
2020 Oct 13
3
[PATCH] drm/nouveau/device: fix changing endianess code to work on older GPUs
...if (!nvkm_device_endianness(device)) {
- nvdev_error(device,
- "GPU not supported on big-endian\n");
- ret = -ENOSYS;
- goto done;
- }
+ nvdev_error(device,
+ "Couldn't switch GPU to CPUs endianess\n");
+ ret = -ENOSYS;
+ goto done;
}
boot0 = nvkm_rd32(device, 0x000000);
--
2.26.2
2016 Dec 12
2
[PATCH] drm/nouveau: fix unknown chipset for GTX 1060
...device->chip = &nv12b_chipset; break;
case 0x130: device->chip = &nv130_chipset; break;
case 0x134: device->chip = &nv134_chipset; break;
+ case 0x136: device->chip = &nv136_chipset; break;
default:
nvdev_error(device, "unknown chipset (%08x)\n", boot0);
goto done;
--
2.1.4
2014 Feb 13
0
nouveau init unknown opcode error, when CONFIG_DRM_NOUVEAU=y
...15 AM, Kui Zhang <kuizhang at gmail.com> wrote:
> Hello,
>
> When CONFIG_DRM_NOUVEAU=y, I get following error. Blank screen after initrd.
>
> This was in the dmesg.
>
> [ 0.282559] [drm] hdmi device not found 1 0 1
> [ 0.282688] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x046800a3
> [ 0.282693] nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46)
> [ 0.282696] nouveau [ DEVICE][0000:01:00.0] Family : NV40
> [ 0.284293] nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image...
> [ 0.366261] nouveau [ VBIOS][0000:01:00.0] ... ch...
2014 Sep 08
1
Extend reserved memory on 0xfc000000
Hi
This patch correct on usb keyboard acces on number when enter via Ctrl
+ Alt + F12 on vt after Xorg running.Without this patch when enter on
vt vas unable to use numbers from NumLock an only numbers from main
keyboard.
nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x046f00a3
nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46)
nouveau [ DEVICE][0000:01:00.0] Family : NV40
nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image...
nouveau [ VBIOS][0000:01:00.0] ... appears to be valid
nouveau [ VBIOS][0000:01:00.0] using image from PRAMIN...
2014 Jun 26
2
[PATCH v3 1/3] drm/nouveau: support for probing platform devices
...Nouveau devices declared using the device tree
>>> or platform data. This driver currently supports GK20A on Tegra
>>> platforms and is only compiled for these platforms if Nouveau is
>>> enabled.
>>>
>>> Nouveau will probe the chip type itself using the BOOT0 register, so all
>>> this driver really needs to do is to make sure the module is powered and
>>> its clocks active before calling nouveau_drm_platform_probe().
>>>
>>> Heavily based on work done by Thierry Reding.
>>>
>>> Signed-off-by: Thierry...
2020 Oct 06
1
[PATCH] device: return error for unknown chipsets
...engine/device/base.c
> +++ b/drm/nouveau/nvkm/engine/device/base.c
> @@ -3149,6 +3149,7 @@ nvkm_device_ctor(const struct nvkm_device_func *func,
> case 0x168: device->chip = &nv168_chipset; break;
> default:
> nvdev_error(device, "unknown chipset (%08x)\n", boot0);
> + ret = -ENOSYS;
> goto done;
> }
>
2014 Mar 25
2
nouveau module not loading
...ia GeForce Go 7900 GS video card. I installed latest debian system
with kernel 3.13-1-amd64 on it, but unfortunately nouveau driver doesn't
work. When I load nouveau module following messages will appear in syslog:
Mar 25 11:50:53 ivnb kernel: [ 2703.329287] nouveau [
DEVICE][0000:01:00.0] BOOT0 : 0x049800a2
Mar 25 11:50:53 ivnb kernel: [ 2703.329293] nouveau [
DEVICE][0000:01:00.0] Chipset: G71 (NV49)
Mar 25 11:50:53 ivnb kernel: [ 2703.329298] nouveau [
DEVICE][0000:01:00.0] Family : NV40
Mar 25 11:50:53 ivnb kernel: [ 2703.333377] nouveau [
VBIOS][0000:01:00.0] checking PRAMIN fo...
2015 Feb 09
17
[Bug 89047] New: linux-3.19 nvd9 Invalid rom content
...rnel command line: BOOT_IMAGE=/boot/vmlinuz-3.19.0-gentoo
root=/dev/sda3 ro quiet splash i915.lvds_downclock=1
init=/usr/lib/systemd/systemd drm.rnodes=1 reboot=a nouveau.pstate=1
[ 7.980357] nouveau 0000:01:00.0: enabling device (0004 -> 0007)
[ 7.980901] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x0d9160a1
[ 7.980904] nouveau [ DEVICE][0000:01:00.0] Chipset: GF119 (NVD9)
[ 7.980906] nouveau [ DEVICE][0000:01:00.0] Family : NVC0
[ 8.034908] nouveau 0000:01:00.0: Invalid ROM contents
[ 8.035060] nouveau ![ VBIOS][0000:01:00.0] unable to locate usable image
[ 8.035114]...
2013 Dec 06
2
Regression: drm/nouveau/clk: implement power state and engine clock control in core (7c856522069755ab9d163a24ac332cd3cb35fe30) breaks GeForce 9400 on Intel Mac Mini Model November 2010 model
Hello Ilia,
> > [ 7.569394] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x0ac080b1
> > [ 7.569460] nouveau [ DEVICE][0000:02:00.0] Chipset: MCP79/MCP7A (NVAC)
> > [ 7.569530] nouveau [ DEVICE][0000:02:00.0] Family : NV50
> > [ 7.571151] nouveau [ VBIOS][0000:02:00.0] checking PRAMIN for image...
> > [ 7.633082] nouveau [...
2017 Feb 14
1
[PATCH] drm/nouveau/core: recognise GP107 chipset
...device->chip = &nv130_chipset; break;
case 0x134: device->chip = &nv134_chipset; break;
case 0x136: device->chip = &nv136_chipset; break;
+ case 0x137: device->chip = &nv137_chipset; break;
default:
nvdev_error(device, "unknown chipset (%08x)\n", boot0);
goto done;
--
2.9.3