Re: [Devil-linux-develop] [Devil-Linux-discuss] r8169 network driver fails to load in DL 1.2.15

[Serge L. <fi...@in...>]

Hello,

Geir Inge wrote:

> Installing the 1.3.6 release on a usb stick with the included
> install-on-usb script gives the same problems as the 1.5.12 release
> (run on a ubuntu hardy machine) :
> 
> 1) selecting lilo as the bootloader, the script fails:
> ...
The script tries to copy the files which are absent in the system. I don't know
if it's a recently added to the script bug or differences between 1.3 and 1.2
systems. I'll look.

> 
> 2) selecting syslinux as bootloader, the script fails:
> 
> Installing syslinux MBR
> 0+1 records in
> 0+1 records out
> 404 bytes (404 B) copied, 0.00895628 s, 45.1 kB/s
> installing SysLinux boot sector
> umount: /tmp/syslinux.mnt.4674.0: device is busy
> umount: /tmp/syslinux.mnt.4674.0: device is busy
> Install failed!
> syncing and unmounting (this could take a while)
I've checked it from DL and it looks working.

	This will install DL on "/dev/hda" using the "syslinux" bootloader.
	All data on device /dev/hda2 will be lost, continue ?  (y/n) y

	Last chance, do you really want to continue ?  (y/n) y
	Installing syslinux MBR
	0+1 records in
	0+1 records out
	404 bytes (404 B) copied, 0.0128979 s, 31.3 kB/s
	installing SysLinux boot sector
	copying files
	copying image of CD in /dev/hdc to device mounted on 				
/tmp/tmp-install2usb/disk-mnt/bootcd.iso
	153320+0 records in
	153320+0 records out
	313999360 bytes (314 MB) copied, 79.4215 s, 4.0 MB/s
	syncing and unmounting (this could take a while)

Maybe it's the consequence of previous unsuccessful attempts? If not, and you
are able to reproduce the error may I  ask you to gather debug information?

> Selecting grub (no serial), the script fails (work ok on the 1.2.15
> release) with:
> 
> Configuring Grub boot sector and menu...
> Do you want to edit the grub menu file  (y/n) n
> Probing devices to guess BIOS drives. This may take a long time.
> ./install-on-usb: line 119:  5069 Segmentation fault      $grub_shell
> --batch --device-map=$device_map  > /dev/null <<-EOF
> root $root_drive
> setup $force_lba $install_drive
> quit
> EOF

PAX: From 10.1.6.104: execution attempt in: <anonymous mapping>,
4e0db000-4e4de000 4e0db000
PAX: terminating task: /sbin/grub(grub):2722, uid/euid: 0/0, PC: 4e144c0e, SP:
4e144ac8
PAX: bytes at PC: b9 f0 4b 14 4e e9 fc 22 f1 b9 08 4e 14 4e 00 4e 14 4e 68 b6
PAX: bytes at SP-4: 00000000 0804b685 00000001 00000000 00000200 4e144af4
0000003f 00000200 00000000 4e144e01 00000009 0000003e 4e14d200 00000200 00000000
00000001 4e144b44 0804cac5 00000080 00000001 00000000

So, it's grsecurity's side effect. I'm going to update grsecurity and PAX to the
latest version and check if the problem goes away.

--
Serge